Act! phone integration
The Act! Web API is an IIS app you install on your own server, and every request needs an Act-Database-Name header. Here is how Allo logs calls to Act!.
app.act.com/contactsActivity
How it connects
Allo connects to Act! through Zapier today.
Licensed operator
Registered telecom operator in France (ARCEP).
Its own network
Allo runs its own VoIP infrastructure, not resold.
GDPR compliant
Your call data stays yours, handled to GDPR.
In the Claude directory
Allo's MCP server is in the Claude connectors directory.
What flows between Allo and Act!
Allo handles the calls and texts. Act! stays the system of record. Here is what moves between them, automatically.
Call Answered
Triggers when a call is answered.
Call Completed
Triggers when a call ends, with result, duration, recording and AI summary.
Call Received
Triggers when an incoming call starts ringing.
Call Triggered
Triggers when an outbound call is initiated.
Missed Call
Triggers when a call is missed.
SMS Received
Triggers when an SMS is received on one of your Allo numbers.
Connect Allo to Act!
Because Act! has a public API, Allo connects over that API and webhooks. These are the API surfaces you point at Act!: a small, focused REST API, JSON in and JSON out, with webhooks for real-time events.
Search your call history. Every record includes transcripts, AI summaries, recording URLs, IVR selections and transfer chains.
Full CRUD on your contact database. Create, fetch by ID, update and search, with engagement data baked into every response.
Send SMS programmatically from any of your Allo numbers. Dedicated endpoints for US and France, both in E.164 format.
Subscribe a URL to call, SMS and contact events. Full envelope payloads, no secondary fetch to enrich the data.
Pull the whole thread for a contact: calls and SMS stitched together, in order, with pagination built in from day one.
List every Allo number on your account. Use it to route, filter or match a number to an owner without hardcoding.
Native or Zapier
The honest version: here is exactly how the connection is made today, and what is not built yet.
Not built yet for Act!
Zapier3 triggers, 7 actions published
Why CRM teams add Allo to Act!
The calling, texting and AI that sit right on your Act! records.
Click to call
Dial any number in one click, from your CRM or browser.
Call Recording & Transcription
Record and transcribe every call, searchable in seconds.
AI Summaries
Every call written up automatically, ready to share.
Post-Call Actions
AI drafts the follow-up email, SMS and CRM update.
Power Dialer
Work a call list back to back, no manual dialing.
SMS / MMS
Two-way business texting with media and voice notes.
Allo and Act!, answered
No. The Act! Web API is an IIS application you install on your own Act! Premium for Web server. Every customer has a different host, and the vendor sample uses localhost. You need to expose it over TLS for Allo to reach it.
Almost always the Act-Database-Name header. It has to name the exact Act! database, and valid credentials with the wrong or missing database name are rejected.
History. In Act!, Activity is scheduled work and shows up on the calendar. History is the record of what happened. Writing a completed call as an Activity puts it in the wrong place entirely.
Act! contacts can carry businessPhone, mobilePhone, homePhone and faxPhone, plus extension, country code and mask fields for each. Allo checks the mobile and business numbers first, because those are the ones customers actually dial.
No. The API version is the installed build number, observed as 1.1.1272.1 on the vendor's demo server. Two customers on the same product can expose different endpoints until they upgrade.
Request a formal Act! integration
Tell us about your team and we'll build the Act! integration and get you early access. The more teams that ask, the sooner it ships.
- Native calling, texting and AI call notes inside Act!
- Every call logged to the right record, automatically
- We build it for your team and give you early access