AlloClose logo

Close phone integration

Close already has a power dialer. Here is exactly what an Allo phone layer adds, what it writes to /activity/call/, and where Close is simply better on its own.

How it connects

Allo connects to Close 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.

Endpoints

Connect Allo to Close

Because Close has a public API, Allo connects over that API and webhooks. These are the API surfaces you point at Close: a small, focused REST API, JSON in and JSON out, with webhooks for real-time events.

CallsREAD

Search your call history. Every record includes transcripts, AI summaries, recording URLs, IVR selections and transfer chains.

GET/v1/api/calls
ContactsREAD & WRITE

Full CRUD on your contact database. Create, fetch by ID, update and search, with engagement data baked into every response.

GET/v1/api/contacts
POST/v1/api/contacts
PUT/v1/api/contacts/:id
SMSSEND

Send SMS programmatically from any of your Allo numbers. Dedicated endpoints for US and France, both in E.164 format.

POST/v1/api/sms
POST/v1/api/sms/fr
WebhooksREAL-TIME

Subscribe a URL to call, SMS and contact events. Full envelope payloads, no secondary fetch to enrich the data.

GET/v1/api/webhooks
POST/v1/api/webhooks
DEL/v1/api/webhooks/:id
ConversationsREAD

Pull the whole thread for a contact: calls and SMS stitched together, in order, with pagination built in from day one.

GET/v1/api/conversations
Phone NumbersREAD

List every Allo number on your account. Use it to route, filter or match a number to an owner without hardcoding.

GET/v1/api/phone-numbers

Native or Zapier

The honest version: here is exactly how the connection is made today, and what is not built yet.

Native Allo integration

Not built yet for Close

Zapier

25 triggers, 46 actions published

Allo and Close, answered

No, and you should not want it to. Close's power and predictive dialers are good and deeply wired into the lead record. Allo covers inbound, the AI receptionist, and countries or teammates Close does not reach.

As a call activity at /activity/call/, attached to the contact and the lead. It carries direction, duration, a disposition and the recording URL, so it looks like any other Close call in the activity feed.

The call object has no transcript field, so the AI summary and transcript link go into the call body rather than a dedicated field. Close does expose a New Call Transcript trigger for its own calls, but that is Close's transcription, not Allo's.

Pagination is hard capped at 10,000 objects, so large backfills are windowed by date_created rather than paged straight through. Plan for that if you are migrating years of calls.

It can, if you leave both running. Close reports on call_method values of regular, power and predictive. Allo calls arrive as logged activities, so decide up front which system owns the outbound number and keep dial session reporting in one place.

Request a formal Close integration

Tell us about your team and we'll build the Close integration and get you early access. The more teams that ask, the sooner it ships.

  • Native calling, texting and AI call notes inside Close
  • Every call logged to the right record, automatically
  • We build it for your team and give you early access

Prefer to talk it through? Book a call