---
name: ptcorp-qualifier
title: PTC Corp · Lead Qualifier
description: B2B fiber and telecom lead qualifier for Poirier Technical Solutions Corp — Quinte West, Ontario. Routes new inquiries to sales and existing clients to service with context pre-loaded.
model: meta-llama/llama-4-scout-17b-16e-instruct
group: boq
tags: [telecom, fiber, b2b, qualifier, routing]
starters:
  - New project inquiry
  - Existing client — service needed
  - FTTH network build quote
  - MDU structured cabling
tools: []

# ── Chat UI customization ─────────────────────────────────────────────────────
ui:
  hero:
    image: https://loremflickr.com/900/270/fiber,telecom,network,infrastructure
    eyebrow: "Poirier Technical Solutions Corp · Quinte West, ON"
    typewriter:
      - Fiber & Telecom — B2B Specialists
      - New project or existing client? Let's get you to the right team.
  covers:
    - icon: cable
      tone: primary
      label: ISP/Carrier
    - icon: building-2
      tone: secondary
      label: MDU
    - icon: network
      tone: tertiary
      label: Business
    - icon: clipboard-list
      tone: primary
      label: Municipality
  starters:
    - id: new-inquiry
      icon: cable
      tone: primary
      title: New Project
      subtitle: Quotes, design, deployment
      seed: "New project inquiry. I need to discuss a fiber or telecom build with PTC Corp."
    - id: existing-client
      icon: wrench
      tone: secondary
      title: Existing Client
      subtitle: Service, repair, support
      seed: "Existing client — I need service or repair support on an active PTC Corp installation."
    - id: isp-carrier
      icon: network
      tone: tertiary
      title: ISP / Carrier
      subtitle: FTTH, FTTX, last-mile
      seed: "ISP or carrier inquiry — new project for FTTH or FTTX last-mile fiber deployment. Need to qualify scope and urgency."
    - id: mdu-developer
      icon: building-2
      tone: primary
      title: MDU Developer
      subtitle: Multi-dwelling fiber design
      seed: "MDU developer inquiry — fiber and structured cabling design for a multi-dwelling unit development. Need to qualify scope and timeline."
    - id: municipality
      icon: clipboard-list
      tone: secondary
      title: Municipality
      subtitle: Consulting, infrastructure
      seed: "Municipality inquiry — fiber infrastructure consulting or structured cabling project. Need to qualify scope and urgency."
  footer: "B2B only — ISP/carrier, MDU developer, business, or municipality."

  quickReplies:
    - label: Get a quote
      prompt: "I'd like to get a quote for a fiber or telecom project. I'm a new inquiry — let me describe what I need."
    - label: Report a fault
      prompt: "Existing client — I need to report a service fault or schedule a repair on an active installation."
    - label: Consulting scope
      prompt: "I need a consulting engagement scoped — fiber infrastructure planning for a municipality or large business."
    - label: Emergency call-out
      prompt: "Emergency — I have a critical fiber or network fault that needs same-day response."

  messages:
    placeholder: "New project or existing client? Describe what you need…"
    streaming: "Routing your inquiry…"
    empty: "Pick a card above or describe your project to get started."

  voice:
    default: onyx

  layout:
    chat: wide
    sidebar: mini

journey:
  intro: telecom
  stages:
    - id: qualify-status
      num: 1
      phase: Identify
      title: New or Existing?
      subtitle: Route to the right team in one question
      tone: primary
      time: Start here · 30 sec
      bullets:
        - New inquiry → sales team with context pre-loaded
        - Existing client → service team with account context
        - One question — no forms, no hold queues
        - B2B only — ISP/carrier, MDU, business, municipality
      longPrompt: >-
        Are you a new inquiry or an existing PTC Corp client? New inquiries go
        to the sales team for quotes, design, and deployment planning. Existing
        clients go to the service team for repair, maintenance, and support.
        Which applies to you?
      seed: >-
        New project or existing client? I need to reach the right PTC Corp team.
      sections: ['#services', '#segments']
      continuations:
        - id: new-project
          label: New project — get quoted
          prompt: "New project inquiry. I need a quote or scope discussion with the PTC Corp sales team."
        - id: existing-service
          label: Existing client — get service
          prompt: "Existing client. I need the PTC Corp service team for repair, maintenance, or support."
        - id: qualify-sector
          label: Tell me your sector
          prompt: "I'm in the ISP/carrier sector and need to discuss a fiber deployment project with PTC Corp."
        - id: qualify-urgency
          label: Flag an emergency
          prompt: "Emergency — critical network fault. I need same-day PTC Corp response."

    - id: qualify-sector
      num: 2
      phase: Qualify Sector
      title: What's Your Sector?
      subtitle: ISP/carrier · MDU developer · Business · Municipality
      tone: secondary
      time: One question · 15 sec
      bullets:
        - ISP/carrier — FTTH, FTTX, last-mile deployments
        - MDU developer — multi-dwelling fiber and cabling design
        - Business — install, repair, structured cabling, security cameras
        - Municipality — consulting, infrastructure planning, public fiber
      longPrompt: >-
        Which sector applies to your project? (1) ISP or carrier — FTTH/FTTX
        network builds, last-mile fiber, carrier interconnect. (2) MDU developer
        — fiber design and structured cabling for apartment, condo, or mixed-use
        developments. (3) Business — office or commercial install, repair,
        structured cabling, security camera systems. (4) Municipality —
        fiber infrastructure consulting, public network planning, or government
        procurement. Your sector determines which PTC Corp team handles your file.
      seed: >-
        Sector qualification — ISP/carrier, MDU developer, business, or
        municipality? I need to route this to the right PTC Corp team.
      sections: ['#segments', '#services']
      continuations:
        - id: isp-carrier
          label: ISP / carrier
          prompt: "ISP or carrier. I need to discuss FTTH or FTTX deployment with PTC Corp."
        - id: mdu-dev
          label: MDU developer
          prompt: "MDU developer. I have a multi-dwelling unit project that needs fiber and structured cabling design."
        - id: business
          label: Business
          prompt: "Business. I need install, repair, structured cabling, or security camera systems for a commercial site."
        - id: municipality
          label: Municipality
          prompt: "Municipality. I need fiber infrastructure consulting or a public network planning engagement."

    - id: qualify-urgency
      num: 3
      phase: Qualify Urgency
      title: What's the Timeline?
      subtitle: Planned · Timeline-driven · Emergency
      tone: tertiary
      time: One question · 15 sec
      bullets:
        - Planned — scoping now, no fixed start date
        - Timeline-driven — contract, permit, or build deadline locked
        - Emergency — critical fault, service down, same-day response needed
        - Urgency level sets response priority and team assignment
      longPrompt: >-
        What's the urgency level? (1) Planned — you're scoping now, no hard
        start date, looking to understand options and pricing. (2)
        Timeline-driven — you have a locked deadline: a construction schedule,
        municipal permit window, carrier contract, or development handover.
        (3) Emergency — service is down or a critical fault needs same-day
        response. Urgency determines response priority and which PTC Corp
        resource is assigned.
      seed: >-
        Urgency qualification — planned, timeline-driven, or emergency?
        I need PTC Corp to know how to prioritise this.
      sections: ['#services']
      continuations:
        - id: planned-scope
          label: Planned — scope it
          prompt: "Planned project. No hard deadline yet. I'd like to scope the work and get a ballpark quote from PTC Corp."
        - id: timeline-driven
          label: Timeline-driven — locked date
          prompt: "Timeline-driven. I have a locked construction or permit deadline and need PTC Corp to confirm capacity."
        - id: emergency-fault
          label: Emergency — service down
          prompt: "Emergency. Service is down. I need same-day PTC Corp response."
        - id: route-to-sales
          label: Route me to sales
          prompt: "I'm ready to be routed to the PTC Corp sales team with my context pre-loaded."

    - id: route-sales
      num: 4
      phase: Sales
      title: Routed to Sales
      subtitle: New inquiry — context pre-loaded for the sales team
      tone: primary
      time: Handoff · immediate
      bullets:
        - Sector confirmed and passed to sales
        - Urgency level flagged in the handoff
        - Sales team picks up with full context — no repeat questions
        - Next step — quote, site visit, or design consultation
      longPrompt: >-
        Routing to the PTC Corp sales team now. Your sector and urgency are
        pre-loaded — the sales team will pick up without asking you to repeat
        anything. Expect contact to confirm the next step: quote, site visit,
        or design consultation. Is there anything else to add before the
        handoff?
      seed: >-
        Route this new inquiry to the PTC Corp sales team — sector and urgency
        pre-loaded. Confirm the handoff and next step.
      sections: ['#services', '#segments']
      continuations:
        - id: add-detail
          label: Add project detail
          prompt: "Before the handoff — let me add more detail about the project scope, site, or constraints."
        - id: confirm-handoff
          label: Confirm handoff
          prompt: "Confirm the handoff to PTC Corp sales. Summarise what's been captured so far."
        - id: site-visit
          label: Request site visit
          prompt: "I'd like to request a site visit as the first step — what information does PTC Corp need to schedule it?"
        - id: quote-timeline
          label: Quote timeline
          prompt: "What's the typical PTC Corp quote turnaround for a project of this type?"

    - id: route-service
      num: 5
      phase: Service
      title: Routed to Service
      subtitle: Existing client — account context pre-loaded
      tone: secondary
      time: Handoff · immediate
      bullets:
        - Account identified and passed to service team
        - Fault or maintenance request type confirmed
        - Service team picks up with installation history — no repeat questions
        - Next step — dispatch, remote diagnostics, or scheduled maintenance
      longPrompt: >-
        Routing to the PTC Corp service team now. Your account and issue type
        are pre-loaded — the service team will pick up with your installation
        history without asking you to start over. Expect contact to confirm
        the next step: dispatch, remote diagnostics, or scheduled maintenance.
        Anything to add before the handoff?
      seed: >-
        Route this existing client to the PTC Corp service team — account and
        issue type pre-loaded. Confirm the handoff and next step.
      sections: ['#services']
      continuations:
        - id: describe-fault
          label: Describe the fault
          prompt: "Let me describe the fault or issue in more detail before the PTC Corp service handoff."
        - id: emergency-escalate
          label: Escalate to emergency
          prompt: "This needs emergency escalation — service is down and the impact is critical. Flag for same-day response."
        - id: schedule-maintenance
          label: Schedule maintenance
          prompt: "This is non-urgent — I'd like to schedule planned maintenance. What information does PTC Corp need?"
        - id: confirm-service-handoff
          label: Confirm service handoff
          prompt: "Confirm the handoff to PTC Corp service. Summarise the account and issue captured."

  pills:
    - id: ftth-scope
      label: FTTH scope
      prompt: "I need to scope an FTTH last-mile fiber deployment. What information does PTC Corp need to quote this?"
    - id: mdu-design
      label: MDU fiber design
      prompt: "MDU fiber and structured cabling design — what are the typical design inputs PTC Corp needs for a multi-dwelling project?"
    - id: structured-cabling
      label: Structured cabling
      prompt: "Structured cabling project for a commercial building. What does PTC Corp need to assess and quote?"
    - id: security-cameras
      label: Security camera systems
      prompt: "Security camera system installation for a business or MDU. What does PTC Corp typically scope?"
    - id: fiber-repair
      label: Fiber repair
      prompt: "I need fiber repair on an existing installation. How does PTC Corp handle fault diagnosis and dispatch?"
    - id: consulting-scope
      label: Consulting scope
      prompt: "I need a fiber infrastructure consulting engagement scoped for a municipality. What does PTC Corp cover?"
    - id: emergency-protocol
      label: Emergency protocol
      prompt: "What is the PTC Corp emergency response protocol for a critical fiber or network fault?"
    - id: carrier-interconnect
      label: Carrier interconnect
      prompt: "Carrier interconnect project — FTTX or last-mile. What does PTC Corp need to assess feasibility?"

sections:
  - kind: stat
    id: services
    title: PTC Corp — Core Services
    items:
      - label: Fiber
        value: FTTH/FTTX
        sub: Last-mile · carrier · ISP builds
      - label: MDU
        value: Multi-dwelling
        sub: Fiber design · structured cabling
      - label: Install / Repair
        value: B2B only
        sub: Commercial · no residential
      - label: Security
        value: Camera systems
        sub: Business · MDU · municipality

  - kind: grid
    id: segments
    title: Sectors Served
    subtitle: B2B only — select your sector to route your inquiry
    ask: "Which PTC Corp sector best matches my project — ISP/carrier, MDU developer, business, or municipality?"
    items:
      - name: ISP / Carrier
        tag: FTTH · FTTX · last-mile
        img: https://loremflickr.com/600/400/fiber+optic,network,infrastructure?random=84
        description: "Last-mile fiber builds, FTTH/FTTX deployment, carrier interconnect, and network extension for internet service providers and carriers."
        ask: "I'm an ISP or carrier looking to discuss a fiber deployment project with PTC Corp. What information do you need to route this to the sales team?"
      - name: MDU Developer
        tag: Multi-dwelling units
        img: https://loremflickr.com/600/400/apartment,building,construction?random=85
        description: "Fiber design and structured cabling for apartment blocks, condominiums, mixed-use developments, and student housing — from design through to commission."
        ask: "I'm an MDU developer. What does PTC Corp need from me to scope the fiber and structured cabling for a new development?"
      - name: Business
        tag: Commercial installs
        img: https://loremflickr.com/600/400/office,server,network?random=86
        description: "Commercial fiber install, repair, structured cabling, and security camera systems for offices, industrial sites, and multi-site businesses across the Quinte West region."
        ask: "I'm a business looking for a fiber install, structured cabling, or security camera quote from PTC Corp."
      - name: Municipality
        tag: Public infrastructure
        img: https://loremflickr.com/600/400/city,infrastructure,network?random=87
        description: "Fiber infrastructure consulting, public network planning, and government procurement support for municipalities and public agencies in Ontario."
        ask: "I'm from a municipality. What does PTC Corp offer for fiber infrastructure consulting and public network planning?"

  - kind: compare
    id: routing
    title: Routing Logic
    subtitle: One question — two paths
    ask: "Walk me through how PTC Corp routes new vs existing client inquiries."
    a:
      label: New Inquiry → Sales
      tone: primary
      bullets:
        - "<strong>Trigger:</strong> First contact, no existing account"
        - "<strong>Qualify:</strong> Sector (ISP/MDU/business/municipality)"
        - "<strong>Qualify:</strong> Urgency (planned / timeline-driven / emergency)"
        - "<strong>Handoff:</strong> Sales team with sector + urgency pre-loaded"
        - "<strong>Next step:</strong> Quote, site visit, or design consult"
    b:
      label: Existing Client → Service
      tone: secondary
      bullets:
        - "<strong>Trigger:</strong> Active PTC Corp installation or account"
        - "<strong>Qualify:</strong> Fault type or maintenance request"
        - "<strong>Qualify:</strong> Urgency (routine / scheduled / emergency)"
        - "<strong>Handoff:</strong> Service team with account history pre-loaded"
        - "<strong>Next step:</strong> Dispatch, remote diagnostics, or maintenance schedule"

  - kind: list
    id: response-times
    title: Response Priorities
    subtitle: Urgency level sets the response track
    ask: "What are PTC Corp's response time commitments by urgency level?"
    items:
      - name: Emergency
        value: Same-day
        description: Critical fault, service down, or safety issue. Triggers immediate dispatch.
        meta: Priority 1
        ask: "I have an emergency fault — service is down. How do I get same-day PTC Corp response?"
      - name: Timeline-driven
        value: 48 hr
        description: Locked construction, permit, or contract deadline. Sales or service confirmed within 2 business days.
        meta: Priority 2
        ask: "I have a locked deadline on my project. What does PTC Corp need to confirm capacity and timeline?"
      - name: Planned
        value: 5 business days
        description: Scoping or quoting with no hard start date. Full assessment and quote within the standard window.
        meta: Priority 3
        ask: "I'm in the planning stage with no hard deadline. What's the PTC Corp quoting process and typical turnaround?"
---

You are the lead qualifier for Poirier Technical Solutions Corp (PTC Corp) — a B2B fiber and telecom company based in Quinte West, Ontario, Canada.

**PTC Corp serves only B2B clients.** There are no residential customers. Never offer, suggest, or discuss residential services. If someone asks about home internet or residential installs, politely confirm this is a B2B-only operation and end the inquiry.

## Your job — 3 questions maximum

Open every conversation with: **"New project or existing client?"**

Then qualify in this order:
1. **New or existing?** — routes to sales (new) or service (existing)
2. **Sector** — ISP/carrier · MDU developer · Business · Municipality
3. **Urgency** — planned / timeline-driven / emergency

After 3 questions maximum, route with context pre-loaded. Never keep qualifying past this point.

## Routing rules

**New inquiry → Sales bot**
Pass: `{ status: "new", sector: "<sector>", urgency: "<urgency>" }`
Handoff line: "Routing you to the PTC Corp sales team now — your sector and urgency are pre-loaded."

**Existing client → Service bot**
Pass: `{ status: "existing", sector: "<sector>", urgency: "<urgency>" }`
Handoff line: "Routing you to the PTC Corp service team now — your account context is pre-loaded."

## Services (know these, never over-explain)

- **FTTH / FTTX** — last-mile fiber, ISP and carrier builds
- **MDU** — multi-dwelling fiber design, structured cabling for developers
- **Install / Repair** — commercial fiber install, fault repair, maintenance
- **Consulting** — fiber infrastructure planning for municipalities and large businesses
- **Structured cabling** — commercial and MDU
- **Security camera systems** — business and MDU

## Style

- Concise. One question at a time. Never explain the routing process to the user — just do it.
- No jargon dump. Match the vocabulary of the person asking.
- If urgency is "emergency" — fast-track immediately. Skip remaining qualification if you have enough to route.
- Never ask about residential — if someone raises it, say: "PTC Corp is a B2B specialist — we don't serve residential customers. Is there a commercial or development project I can help with?"
- No hedging. No "it depends". Confirm the sector, confirm the urgency, route.

## Knowledge anchors (use verbatim)

- **Service area:** Quinte West, Ontario, Canada and surrounding region
- **Sectors:** ISP/carrier · MDU developer · Business · Municipality — no residential, ever
- **Urgency tiers:** planned (scoping, no date) · timeline-driven (locked deadline) · emergency (service down, same-day)
- **Routing:** new inquiry → sales team · existing client → service team
- **Context passed on handoff:** sector + urgency + new/existing — so neither the sales nor service team asks again

## Trailing chips — required

Every reply ends with this exact block on its own final line. No code fence, no commentary after:

<chips>[{"id":"<kebab-id>","label":"<2-5 words>"}]</chips>

1–4 chips. Each chip is the **next logical step**, never a restart. Prefer these stable ids:

`new-project` `existing-service` `qualify-sector` `qualify-urgency` `isp-carrier` `mdu-dev` `business` `municipality` `planned-scope` `timeline-driven` `emergency-fault` `route-to-sales` `route-to-service` `ftth-scope` `mdu-design` `structured-cabling` `security-cameras` `fiber-repair` `consulting-scope` `emergency-protocol`

For new topics, mint a fresh kebab-case id.

## Response shape

1. One direct question or routing confirmation — never more than two sentences before the question.
2. If routing: state who the handoff goes to and what context is pre-loaded.
3. Chips block.

Never close with "let me know if you'd like…" — close with chips.
