Technical companion

Keel × Quo: the phone, tied to your ops.

Quo provides the company number, calls, SMS, and AI receptionist. Keel connects it to how your business already runs, so a text is a record and a missed call is a task, not a voicemail nobody plays.

QuoQuo Community ExpertKeel Automation · Tampa Bay, FL
Architecture

Three channels between Quo and your records.

Quo
Quo
  • Company number
  • Calls · SMS · voicemail
  • Shared team inbox
  • AI receptionist
Webhooks
call.completed · message.received → Hub
REST API
Hub sends outbound texts, reads call logs
MCP tools
AI assistant in the Hub can text or look up a contact
Keel Hub
  • Contacts · deals · projects
  • Every call/text on the record
  • Audit log on every action
  • Supabase · RLS
Shared Supabase backend. Same records the client portal reads, scoped by row-level security.
Supported workflows

What we wire up.

Each one is running on Keel's own line today.

Inbound text → lead

message.received webhook matches the number to a contact (or creates one), appends the text, and opens a lead if none is active.

Missed call → callback task

call.completed with no answer creates a follow-up task on the contact and texts the owner a one-line summary.

AI intake → structured record

The AI receptionist transcript is summarized into name, need, and callback window, then written to the deal with the recording link.

Hub → outbound SMS

Staff text from the contact record in the Hub; the message goes out on the company number via Quo's API and is logged.

Assistant tools (MCP)

The Hub's AI assistant can look up a contact's call history or send a templated text, through audited server functions only.

Other CRMs

HubSpot, Jobber, ServiceTitan, QuickBooks contacts. Same webhook pattern, mapped to your system's objects.

Security

Same rules as everything else we build.

Phone data is customer data. It gets the same controls as invoices.

  • Webhook signatures verified; unsigned payloads dropped
  • Quo API keys stored server-side only, never in the browser
  • Every write from a webhook or tool call lands in the audit log
  • Row-level security scopes call and text records per organization and project
  • Recordings and transcripts retained per your policy, deletable on request
Keel AutomationQuo

Keel installs and operates Quo for Tampa Bay businesses. We run our own line on it.

Prefer to start in Quo yourself? Start in Quo with Keel's partner link

Referral disclosure: Keel is a Quo partner and may earn a commission if you subscribe through our link. Our setup and integration fee is the same either way.

Want the full offer?

Setup tiers, the AI receptionist, and the before/after of a shop that switched.

Related: our phone stack case study · operations portals · request a callback

CallText