3.1Healthcare Practice Group[3-1]
DEPLOYED2024-08-14CATEGORYHEALTHCAREHOSTNAMEAGENT.HEALTHGROUP.COMSTATUSACTIVE · REV-AIMPLEMENTATIONInbound triage, after-hours intake, EHR-routed escalation.
↳ See also: §3.1.A operator notes · [REF-31]
FORM GA-2026-2 · FILE NO. KPT.IND.001PAGE I OF VII · COVERPRINTED IN AZ · USA
UNCLASSIFIED · DISTRIBUTION: PUBLIC▲ HANDLE WITH NORMAL CARE
INTERNATIONAL BUSINESS MACHINES — KPT EDITION · TECHNOLOGY INNOVATION FIRM
FIG. I — REFERENCE FOOTAGE · 16/9 · 1080p · STEREO
KPT.WEB / HERO / 02
0:00 / 0:00PLATE · FIG. ISOURCE · VEO 3 · INTERNAL
An Operator’s Manual for a Technology Innovation Firm — Subsystems, Procedures & Specifications.
─── DOCUMENT CONTROL ───
Contents
DOC NO.KPT-2026-2
REVISIONA
DISTRIBUTIONPUBLIC
DATE OF ISSUE08 MAY 2026
SUPERSEDESKPT-2024-1 (REV. C)
CLASSIFICATIONUNCLASSIFIED
FORMGA-2026-2
PREPARED BY
K. P. T. EDITORIAL
APPROVED BY
OFFICE OF THE PARTNER
─── TABLE OF CONTENTS ───
Contents
▲ NOTEThis volume describes the operating procedures for KPT.INDUSTRIES — the vertically integrated parent of KPT Agents and KPT Designs since 2024. Read §1.0 before commissioning a new engagement.
© 2024–2026 KPT INDUSTRIES · ALL RIGHTS RESERVED
CONTINUED ON FOLIO §02 — PHILOSOPHY ►
KPT-INDUSTRIES / OPERATOR MANUALSECTION 1 · PAGE 002GA-2026-2
KPT-INDUSTRIES / OPERATOR MANUALCHAPTER ONE
CHAPTER ONE
1.0 PHILOSOPHY
DOC-ID · KPT/IND/CH1REV · ASTATUS · STABLECLASS · OPERATING PRINCIPLES
§1.1CROSS-VERTICAL PRODUCT DESIGN
KPT Industries designs products that solve customer-touchpoint problems wherever they live — healthcare intake, legal qualification, real-estate showings, hospitality reservations, home-service dispatch. The thesis is that the primitives that make a customer touchpoint smarter, faster, or more reliable are the same primitives across every vertical, and that a product portfolio organized around those primitives compounds far better than one organized around any one industry.
NOTE 1.1.a“Cross-vertical” in this manual means that a single subsystem must deploy into at least three industries with no industry-specific rewrite. KPT Agents clears this bar; KPT Designs clears it by definition.
§1.2IN-HOUSE BUILD, NOT BROKERED
Every KPT Industries subsystem is built, owned, and operated by KPT Industries. Voice infrastructure, web stack, AI orchestration, hosting, and domain operations are all in-house — there are no white-labeled vendors and no third-party rebranding. Templates are not used. Page builders are not used.
NOTE 1.2.a“In-house” in this manual means an Industries operator can answer questions about every layer of the stack without escalation. Subcontracted, opaque, or generated output does not satisfy this definition.
§1.3CUSTOMER-TOUCHPOINT FIRST
Industries enters new product spaces only where there is an identifiable customer touchpoint that can be measurably improved. Internal tooling, B2B middleware, and infrastructure-for-its-own-sake are out of scope. The Operator may at any point challenge a roadmap item by asking “which touchpoint?”; absence of a clear answer is grounds for de-scoping.
▲ NOTE 1.3.aSeverance from the touchpoint must not degrade product function. Any roadmap item whose value disappears when the customer interaction is removed is not a KPT Industries product.
◆ END · CHAPTER 1 ◆
KPT-INDUSTRIES / OPERATOR MANUALCH. 2 · PG. 003GA-2026-2
KPT-INDUSTRIES / OPERATOR MANUALCHAPTER TWO
CHAPTER TWO
2.0 SUBSYSTEM SPECIFICATIONS
DOC-ID · KPT/IND/CH2REV · ASTATUS · STABLECLASS · PRODUCT REFERENCE
KPT Industries currently operates two labeled subsystems. The following enumerates the standard configuration shipped with each. Each subsection documents a single component of the runtime stack, its operating parameters, and any caveats the operator should observe before authorizing release.
■ AZURE · SUBSECTION HEADER■ RED · REFERENCE INDEX■ AMBER · OPERATOR WARNING
§2.1KPT AGENTS [SUBSYSTEM]
Inbound AI voice agents that answer the phone, qualify the caller, and route or escalate.
S
ubsystem module. Routes inbound voice traffic to a Claude-powered agent which qualifies the caller, captures intake, and forwards structured leads back to the studio queue. Operates over a SIP trunk with a fallback to human escalation. Treated as an external bus on the architecture diagram; not bundled with the website runtime.
PARAMETERSTBL.01
RUNTIMETwilio Voice / Pipecat / Anthropic Claude
TRANSPORTSIP · Webhook
LATENCY< 600 ms first-token (typ.)
CAPABILITIESINBOUND · LLM_QUALIFY · BOOK · ESCALATE
VERTICALSHealthcare · Legal · Real Estate · Home Svcs.
AVAILABILITY24/7
◆ WARN ·NOTE:KPT Agents is a labeled subsystem, not a hard dependency of the Industries website runtime. The site renders nominally with the bus offline, but the ‘Start an engagement’ flow falls back to email if the agent line is unreachable.
§2.2KPT DESIGNS [SUBSYSTEM]
Boutique web design studio — hand-coded sites with full source ownership and managed hosting.
B
outique web design module. Provides end-to-end design, hosting, and domain registration. Operator (the client) receives the complete source code, deployment configuration, and DNS records on completion. KPT Designs role becomes consultative once delivery is complete; no proprietary tooling locks the system. See kptdesigns.com →
PARAMETERSTBL.02
STACKNext.js 16 / React 19 / Tailwind 4 / TypeScript
HOSTINGVercel · Edge / Fluid Compute
DOMAINSRegistrar + DNS managed in-house
DELIVERABLESSource · Config · DNS · Handover doc
LOCK-INNone — operator-owned
LEAD TIME2–6 weeks · scope-dependent
NOTE 2.2.a“Hand-coded” means every line of markup is a deliberate choice and every deliberate choice is documented in the source. Generated, scaffolded, or opaque output does not satisfy this definition.
§2.3INDUSTRIES OPERATIONS [BUS]
Shared services that bind the subsystems — engagement intake, billing, and operator support.
PARAMETERSTBL.03
FACILITY4700 S Mill Ave · Tempe, AZ 85282
HOURSMon–Fri · 9:00–18:00 MST
INTAKEinfo@kptindustries.com · agent line on request
BILLINGNet-30 · ACH / wire / card
◆ END · CHAPTER 2 ◆
END OF CHAPTER 2FORM KPT-IND-002 · REV. A
KPT-IND / OPERATOR MANUALCHAPTER 3 · PAGE 005GA-2026-2
KPT-INDUSTRIES / OPERATOR MANUAL§ REFERENCE / CASE-STUDY APPENDIX
§ REFERENCE / CASE-STUDY APPENDIX
3.0 REFERENCE IMPLEMENTATIONS
DOC-ID · KPT/IND/CH3REV · ASTATUS · STABLECLASS · DEPLOYMENT INDEX
The following six (6) entries document deployed reference implementations commissioned of the KPT Industries portfolio between calendar years 2024 and 2026. Each subsection describes scope, vertical, and implementation surface. Cross-references are issued in RFC style.
3.2Counsel & Associates[3-2]
DEPLOYED2024-11-02CATEGORYLEGALHOSTNAMEAGENT.COUNSEL.LAWSTATUSACTIVE · REV-BIMPLEMENTATIONConflict-check intake form, retainer eligibility script, smart escalation.
↳ See also: §3.2.A operator notes · [REF-32]
3.3Cardinal Realty Group[3-3]
DEPLOYED2025-02-19CATEGORYREAL ESTATEHOSTNAMEAGENT.CARDINALRE.COMSTATUSACTIVE · REV-AIMPLEMENTATIONListing inquiry capture, showing scheduler, agent-of-the-day handoff.
↳ See also: §3.3.A operator notes · [REF-33]
3.4Sunbelt Home Services[3-4]
DEPLOYED2025-05-30CATEGORYHOME SERVICESHOSTNAMEAGENT.SUNBELTHS.COMSTATUSACTIVE · REV-AIMPLEMENTATIONService-call intake, dispatch routing, emergency line dispatch.
↳ See also: §3.4.A operator notes · [REF-34]
3.5Mesa Hospitality Collective[3-5]
DEPLOYED2025-09-08CATEGORYHOSPITALITYHOSTNAMEAGENT.MESAHC.COMSTATUSACTIVE · REV-AIMPLEMENTATIONReservation intake, multi-property routing, gift-card surface.
↳ See also: §3.5.A operator notes · [REF-35]
3.6Ironwood Professional Svcs.[3-6]
DEPLOYED2026-01-22CATEGORYPROFESSIONAL SVCS.HOSTNAMEAGENT.IRONWOODPS.COMSTATUSACTIVE · REV-AIMPLEMENTATIONLead qualification, calendar handoff, tax-season overflow.
↳ See also: §3.6.A operator notes · [REF-36]
◆ END · CHAPTER 3 ◆
KPT-IND / OPERATOR MANUALCHAPTER 4 · PAGE 006GA-2026-2
KPT-INDUSTRIES / OPERATOR MANUALCHAPTER FOUR
CHAPTER FOUR
4.0 ENGAGEMENT PROCEDURES
DOC-ID · KPT/IND/CH4REV · ASTATUS · STABLECLASS · OPERATIONAL
§4.1PROCEDURE: INITIAL CONSULTATION
Discovery call to identify which subsystem (Agents, Designs, or both) addresses the Operator’s touchpoint. No-cost, no-commitment.
STEP 1SCHEDULE DISCOVERY CALL · 30 MIN.
STEP 2DOCUMENT SCOPE, TIMELINE, SUCCESS METRICS.
STEP 3RECOMMEND SUBSYSTEM(S) AND ISSUE QUOTE.
! WARNINGDo not proceed to §4.2 without a counter-signed agreement on file. Verbal scope is non-binding.
§4.2PROCEDURE: SUBSYSTEM SELECTION
Subsystem(s) are configured against the signed scope. Iterative review check-ins are mandatory and recorded.
STEP 1SUBSYSTEM CONFIGURATION COMMENCES.
STEP 2WEEKLY REVIEW CHECK-INS.
STEP 3ITERATE UNTIL SPECIFICATIONS MET.
§4.3PROCEDURE: ENGAGEMENT LAUNCH
Promotion of the deliverable from staging to public production. Requires Operator sign-off prior to execution.
STEP 1DEPLOY TO PRIVATE STAGING.
STEP 2OPERATOR (CLIENT) APPROVAL.
STEP 3PUBLIC DEPLOYMENT.
! WARNINGPublic deployment is irreversible without rollback procedure §6.2. Confirm DNS, SSL, and analytics before issuing the launch token.
§4.4PROCEDURE: OPERATIONAL HANDOVER
Transfers full operational ownership to the Operator. Industries retains no production credentials post-handover.
STEP 1TRANSFER SOURCE, CONFIG, AND DNS RECORDS.
STEP 2OPERATOR ACKNOWLEDGES RECEIPT.
STEP 3INDUSTRIES PROVIDES CONSULTATIVE SUPPORT ON REQUEST.
◆ END · CHAPTER 4 ◆
KPT-IND / OPERATOR MANUALCHAPTER 5 · PAGE 007GA-2026-2
KPT-INDUSTRIES / OPERATOR MANUALCHAPTER FIVE
CHAPTER FIVE
5.0 CONTACT · ACTION REQUIRED
DOC-ID · KPT/IND/CH5REV · ASTATUS · OPENCLASS · ENGAGEMENT
5.1 ACTION REQUIRED
The Operator should now schedule an initial consultation. Two pathways are available:
(A)Initiate a new engagement — info@kptindustries.com
(B)Visit operations — 4700 S Mill Ave, Tempe, AZ 85282