BizFalcon AITwilio reporting, computed from the rows.
SMS sends, delivery and reply volume.
- Messages sent and delivered
- Delivery failures
- Spend
Why connect Twilio.
SMS cost and delivery reported next to the campaigns it supported.
What we read from it
- Messages sent and delivered
- Delivery failures
- Spend
You do not have to connect it
Export message logs from the Twilio console and upload the CSV.
Both products were built to run on a file, because an agency cannot always get a client’s login and a brand should not have to grant one to try something.
Disconnecting is one click
Revoke the connection from Settings whenever you like. Reports you already built keep their figures; only the refresh stops.
Twilio bills per segment, not per message. Long messages cost more than they look like they should, and the spend column reflects segments.
Connected or exported, the maths is the same.
Connect or upload
Authorise Twilio from Settings, or drop in the export it already produces. The column mapper handles the naming differences.
It computes, in Python
The engine writes pandas and runs it against your rows. Every figure keeps the code that produced it, so any number on the page opens to its own arithmetic.
You decide
The result lands in ClientFalcon. Agents queue what they find; nothing runs against your account until you approve it.
The rest of the email & sms connectors.
KlaviyoMailchimpActiveCampaignBrevoMailerLiteConstant Contact
See Twilio on your own numbers.
Fourteen days, no card. Connect it, or upload the export you already have and skip the connection entirely.