What is a Role Brain?

A Role Brain is a persistent decision-pattern repository that captures the tacit knowledge and instincts of key personnel. When an executive departs, their Role Brain remains as a corporate asset, allowing a successor to operate at full capacity from Day 1.

How does StackFast differ from standard RAG implementations?

Standard RAG retrieves text without understanding context. StackFast provides a reasoning layer that applies judgment through structured logic, builds persistent Role Brains that compound over time, and enforces knowledge sovereignty through a 3-layer governance gate.

What is Knowledge Sovereignty?

Knowledge Sovereignty means your organization's intelligence never leaks into third-party training sets. Every brain entry is tagged for compliance and M&A readiness, with audit trails generated automatically for EU AI Act, SOC2, and HIPAA compliance.

How does StackFast reduce Key-Person Risk?

StackFast captures executive decision patterns, client relationship nuances, and institutional knowledge into structured Role Brains. When key personnel leave, their judgment and instincts remain as a corporate asset, reducing onboarding time for replacements and preserving institutional intelligence.

Back to Catalog

workflow

AI Receptionist and Call Intake

AI Receptionist and Call Intake is the job-named product wrapper for Quinn's inbound voice transport pilot.

Host and data posture

Where this product is meant to live.

Revenue Desk intake layer; live line remains gated until telephony proof exists.

Commercial shape

Operator-console system

Data posture

Tenant brain required

Approval posture

Operator action

Best demo

StackFast UI

Best daily use

OpenClaw hostedStackFast UIOpenClaw BYOC

Who it is for

Businesses that want an AI receptionist but need approval gates before CRM, service desk, calendar, or follow-up actions execute.

Problem it solves

It gives inbound calls a governed intake path instead of a dark autonomous caller agent.

Activation model

Inquiry first. Live pilot requires OpenAI Realtime billing, phone number/SIP, AI disclosure script, consent policy, A2P SMS approval, receipts persistence, and review screen.

Composition decisions

What is packaged here, and what is not.

These notes prevent agents from splitting proof lanes into duplicate Store products before the repo has a first-class product record, entitlement, and receipt-backed runtime.

RR360 / A2P SMS

composed capability

Repo truth shows app/api/ai-receptionist/sms/route.ts and SMS tests as an A2P-gated receptionist proof lane for repair/remodel. There is no standalone RR360 or SMS Store product with independent checkout, entitlement, or marketplace readiness.

Agent guidance
Use AI Receptionist for inbound call/SMS intake, GrowthOS for reviewed follow-up packets, and OCE for repair/remodel estimating. Do not offer bulk SMS or autonomous outbound.

Proof and source paths

CleverQ PR #34 merged voice transport pilot harness
SIP webhook is hard-gated
Audio-exit MASK probe exists
StackFast MCP intake/status/review_queue/callback_packet facade exists
Inbound SMS webhook returns Twilio MessagingResponse XML while outbound SMS stays A2P-gated

Repo evidence

docs/wiki-manuals/ai-receptionist-call-intake-manual.md
lib/ai-receptionist/mcp-tools.ts
lib/ai-receptionist/loop-persistence.ts
app/api/ai-receptionist/sms/route.ts
app/sms-privacy/page.tsx
app/sms-terms/page.tsx
docs/a2p/A2P-CAMPAIGN-PACKET.md
app/api/mcp/route.ts
../cleverq/src/lib/voice-agent/realtime.ts
../cleverq/src/app/api/voice-agent/realtime/sip-webhook/route.ts

Capabilities

inbound call intake

workflow

Answer inbound calls, qualify callers, and queue external actions for review.

Agent use
Pilot-stage StackFast MCP workflow. Intake creates Desk and CRM callback receipts for business calls; inbound SMS replies are handled by the production Twilio webhook; outbound SMS and live voice routing remain gated.

a2p gated inbound sms intake

workflow

Accept inbound SMS for the receptionist proof lane, parse STOP/HELP/START, and queue review-gated Desk/CRM receipts without live-line or autonomous outbound sends.

Agent use
Use the AI Receptionist product for A2P-gated inbound SMS. The RR360 SMS route is a repair/remodel proof lane and must not be sold as a separate SMS product or bulk outbound campaign tool.

Connector proof

Catalog is not the same as customer-ready.

This product only becomes market-ready after a real host mounts the entitled tools, a safe call succeeds, metering records the event, and a customer-safe receipt exists. Until then, the page shows the strongest proven status without rounding up.

Catalog

Runtime registry and product manifest are present.

Entitlement

Execution requires OAuth or storefront entitlement scope.

Callable

Callable tool proof is incomplete.

Metering

Metering waits on callable execution.

Customer validated

Pending fresh host-surface call receipt.

Runtime registry status

Primary registry

stackfast.ai/api/mcp

Status

pilot mcp

Install gate

Pilot MCP only until live SIP, recording/consent policy, A2P SMS approval, calendar connector policy, and live call/SMS smoke pass.

Callable tools

stackfast.ai_receptionist.intake
stackfast.ai_receptionist.status
stackfast.ai_receptionist.review_queue
stackfast.ai_receptionist.callback_packet

Missing or gated tools

cleverq.voice.turn public manifest
calendar scheduling connector
live SIP consent/recording smoke
A2P campaign approval before outbound SMS send

Quinn is the persona; AI Receptionist and Call Intake is the product name.
No business cell live routing until floor-before-live instrumentation, explicit live-line approval, and recording/consent policy are verified.
RR360/A2P SMS is composed under this product and GrowthOS beachhead context until a standalone product record is ratified.

Install and activate

Connect this product through the StackFast MCP endpoint. Discovery metadata is public; execution uses OAuth and storefront entitlement checks.

MCP URL

https://stackfast.ai/api/mcp

Agent subscription

This product remains request-scope until its checkout, fulfillment, and public-name gates are complete.

Client snippets

ChatGPT

Add StackFast as a custom MCP connector, then approve OAuth when prompted.

Claude

Connect a remote MCP server using the StackFast MCP URL and a tenant-scoped token or OAuth flow.

Cursor

Grok

Add StackFast as a custom MCP connector using the StackFast MCP URL and customer entitlement auth.

Product: AI Receptionist and Call Intake
Product API: https://stackfast.ai/api/store/products/ai-receptionist-call-intake
Pricing API: https://stackfast.ai/api/store/pricing/ai-receptionist-call-intake
Manifest API: https://stackfast.ai/api/store/manifests/ai-receptionist-call-intake
MCP URL: https://stackfast.ai/api/mcp
Auth: oauth_reader_or_storefront_entitlement
Checkout session API: https://stackfast.ai/api/store/checkout/session
Plans:
- Receptionist pilot: Request scope; checkout_ready=false; checkout_url=request_scope
Agent activation:
- Read this product manifest and pricing API.
- If a plan has checkout_ready=true, open its checkout_url or POST product_slug, plan_slug, and customer_email to the checkout session API.
- After Stripe payment, the signed webhook grants storefront_entitlements for the buyer email/account.
- Connect the LLM client to the MCP URL and approve OAuth so tools/list reflects the licensed reader surface.
- Call only tools exposed for that entitlement; unentitled execution must fail closed.

Agent-readable queries

AI receptionist call intakeinbound AI receptionist with approval queueA2P gated SMS receptionistvoice agent for scheduling and transfer