Skip to main content
Twilio handles billions of communications — SMS, voice calls, and WhatsApp messages — making it the richest source of actual customer language most companies ignore. These three jobs pull conversation data from Twilio’s REST API and Conversations API into Mavera’s surfaces (Mave Agent, Brand Voice, Personas, Generate) to analyze SMS patterns, turn call recordings into meeting-style intelligence, and extract persona insights from WhatsApp business conversations.

API Reference Card

All examples use TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, and MAVERA_API_KEY. Twilio uses HTTP Basic Auth with your Account SID as username and Auth Token as password. Find both in your Twilio Console.

Prerequisites

1

Twilio account with messaging

You need an active Twilio account with at least one phone number provisioned for SMS. For WhatsApp, you need a WhatsApp Business Profile approved.
2

Account credentials

Find your Account SID and Auth Token in the Twilio Console dashboard.
3

Call recordings enabled

For Job 2, enable call recording in your TwiML or Studio flows. Recordings are stored as audio files accessible via the Recordings API.
4

Mavera API key

Get your key from Mavera dashboard.
5

Environment variables


Jobs


Rate Limits & Production Notes

Twilio bills per API call and per message. The jobs above make 5-50 API calls per run — negligible cost. However, WhatsApp Business API has a 24-hour reply window and requires pre-approved templates for outbound messages. SMS opt-out compliance (STOP/HELP) is mandatory. Store credentials in env vars. Never log auth tokens. For call recordings, respect retention policies and data privacy regulations. Monitor Mavera credits at Dashboard.

All Integrations

Twilio API Docs

Brand Voice

Personas

Mave Agent

Generate