How to reach Dottie

What happens when someone calls

In English: Twilio hands the call to Vapi. Vapi sends what the caller said through Deepgram (transcription), passes the text to Claude (the brain), gets a response, plays it back through ElevenLabs. When Claude wants to DO something — book a meeting, file a ticket, schedule a wake-up — Vapi pings the worker, the worker fires the tool, and replies back through the chain.

Why Poke isn't replacing Twilio (and why that's correct)

The simple version: Poke is a personal account — only Drey can receive Poke messages because Poke is logged in as Drey. Twilio is a phone number — anyone can text or be texted, like a real cell line.

So when Dottie wants to say something to you, she goes through Poke (no auth-token rotation, no carrier hassles). When she needs to text someone you've never met — say, the prospect who just called and asked for a link — she has to use Twilio (or Telnyx if/when you switch).

Today's status: all 6 of Dottie's "ping Drey" sites already use Poke (took out Twilio there last night). The 3 caller-facing texts still use Twilio because there's no other option for arbitrary phone numbers.

The 22 things Dottie can do

The stack — every external service Dottie uses

The webhook hub (optional)

Dottie has an inbound endpoint at https://dottie-webhook.dreytools.com/webhook/inbound/<source>. If you want Stripe (failed payments), GitHub (CI failures), Sentry (crashes), Uptime Kuma (site down), or anything else to send you alerts — point their webhook URL at this endpoint with a secret query string, set the matching WEBHOOK_SECRET_<SOURCE> in wrangler, and Dottie forwards a 600-char summary to your Poke inbox.

It's optional and idle until you actually configure a source. Each source gets its own secret so a Stripe leak doesn't compromise your GitHub flow.