From question to answer,reminder, or human follow-up
QotBot handles two distinct workflow types — inbound support and outbound reminders. Here's how each works.
Two tracks
Track A handles what comes in. Track B reaches out before customers have to.
Inbound support workflow
Customer reaches out — QotBot answers, routes, or escalates.
Inbound support
- TriggerCustomer calls or texts your number, or submits a web form
- ChannelVoice IVR (DTMF), inbound SMS, or web widget (roadmap)
- ActionQotBot identifies intent and responds from approved knowledge, or routes to the right team
- EscalationComplex, sensitive, or out-of-scope questions escalate to a human with full conversation context
- OutcomeQuestion answered, booking made, or ticket created — with audit trail
Outbound reminder & update workflow
System event triggers a proactive message — QotBot reaches out.
Outbound reminder
- TriggerEvent in a connected system: appointment created, order shipped, trial expiring, payment failed
- ChannelOutbound SMS (available); email (roadmap); voice (roadmap)
- ActionQotBot sends the configured message; recipient can reply to ask questions or confirm
- EscalationReplies that fall outside approved knowledge route to staff; STOP immediately opts out
- OutcomeCustomer or patient informed; response logged; consent state updated
Setting up QotBot
Designed to scale from small teams to higher-volume operations. Most teams complete initial setup within a week.
Connect your channels
Point your phone line to QotBot's number, add the SMS number to your forms, or drop the web widget snippet. QotBot starts receiving on day one.
Load approved knowledge
Add FAQs, policies, escalation rules, and playbooks through the console. QotBot only uses what you give it — it does not generate content from outside your knowledge base.
Configure escalation rules
Define when and how QotBot routes to humans: by topic, keyword, sentiment signal, or explicit request. No conversation reaches a dead end.
Connect your systems
Wire up your calendar, CRM, order system, or EHR via webhook. QotBot can pull live data into responses and trigger messages from system events.
Go live and review
QotBot starts handling inbound and outbound communication. Review outcomes, consent events, escalations, and audit trails from the console.
Voice IVR — Voice v1
QotBot's current voice capability uses DTMF (touch-tone) routing — callers press a number to reach the right team. This is a stable, widely-compatible approach for inbound routing. Natural language voice understanding is on the roadmap as Voice v2.