Skip to content
Telephony and messaging

Telephony and messaging

PULSE has four voice and messaging paths. All of them are off until you configure them.

The carrier settings themselves are admin-only, and they live on the Account page under Messaging — not in the navigation rail. Someone who is not an admin of this instance never sees the carrier fields.

Calls to leads

The one way PULSE calls a lead is an AI call over Twilio (AICallService.PlaceAICall; see AI calls). Every call passes the same guards: an editor or admin places it, the lead’s recorded consent covers that exact number, it is 08:00–21:00 in the lead’s time zone, the number is not on the do-not-call list (an unreadable list refuses the call), the attempt cap holds, and the AI says it is an AI in its first sentence.

The earlier Asterisk path (LeadService.CallLead, the ASTERISK_* and AUDIOSOCKET_ADDR variables) is retired: it dialled with none of those guards.

Browser voice calls

The app’s full-screen call view sends a WebRTC offer to /voice/webrtc/offer. PULSE forwards it to the platform’s shared calling agent at CALLING_AGENT_URL, which carries the audio. PULSE is only the authenticated signaling door.

When CALLING_AGENT_URL is unset, the offer is refused with HTTP 503 and voice calling is not configured: CALLING_AGENT_URL is unset. For signaling tests, PULSE_WEBRTC_SIGNALING_ONLY=true answers offers with PULSE’s local handler, which carries no audio.

Turn-based voice input (/voice/transcribe) needs only the Voxtral server (VOXTRAL_REMOTE_URL). Both voice endpoints require a signed-in caller.

WhatsApp and SMS

PULSE accepts inbound WhatsApp and SMS messages from Twilio at /twilio/message, and answers with its marketing personas: the same set it offers over A2A.

  • Every request must carry a valid Twilio signature (TWILIO_AUTH_TOKEN).
  • Only senders who are contacts in PULSE’s HubSpot account may talk to it. PULSE_WHATSAPP_USER_ID picks whose HubSpot connection is used. The default is to deny.
  • The edge generates text: analysis, content, strategy, research. Creating leads or campaigns and approving content stay behind the signed-in gRPC API.
  • Replies are automatic only when switched on (below). Each one passes PULSE’s guardrails, and the incoming message is treated as data, never as instructions. Replies run as the user set in PULSE_WHATSAPP_USER_ID; with none set, nothing is answered.
  • Automatic replies are off by default. To turn them on, set PULSE_WHATSAPP_AUTOREPLY=true; each reply is a send, so it also needs PULSE_APPLY_ENABLED=true and PULSE_PUBLISH_WHATSAPP (or PULSE_PUBLISH_SMS) not switched off. Otherwise messages are received but not answered.
VariableMeaning
TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKENThe Twilio account
TWILIO_WHATSAPP_FROM, TWILIO_FROM_NUMBERThe WhatsApp sender and the SMS number
PULSE_WHATSAPP_USER_IDThe user whose HubSpot contacts form the allowlist, and as whom replies run
PULSE_WHATSAPP_AUTOREPLYtrue turns automatic replies on (they also need the publish switches). Default: off

Send / Call to a saved contact

PULSE also carries the shared Runink Send / Call layer, the same code FACE and TIDE use, so the allowlist, the per-send confirmation, the rate limit, the body cap, the recording notice and the audit trail behave identically across the three.

  • Only a saved contact can be reached. Admins add contacts on Account → Messaging; a number that is not on the list is refused. A service account can never message or call anyone.
  • The carrier settings are sealed with TIDE_ENVELOPE_KEK. Without that key the page refuses to store a secret rather than writing it in the clear. Contacts, sealed settings and the delivery trail live under $PULSE_DATA_DIR/comms.
  • Variables. TWILIO_ACCOUNT_SID and TWILIO_AUTH_TOKEN come from the secret store (with an environment fallback); TWILIO_WHATSAPP_FROM, TWILIO_FROM_NUMBER and TWILIO_VOICE_FROM are settings. TWILIO_VOICE_FROM is optional and falls back to TWILIO_FROM_NUMBER. What an admin saves on the page overlays the environment.
  • Delivery states are posted back to /comms/twilio/status. Without PULSE_PUBLIC_BASE_URL there is no callback URL to give the carrier, so states stay at accepted.
  • A call speaks and ends. It plays the recording notice first, then PULSE’s greeting and the summary; there is no interactive media leg on this path.