How to connect
The Freshservice integration connects with your Freshservice domain and a Freshservice API key. You need an Allo admin or manager to connect the integration.The Freshservice API is available on every paid Freshservice plan (Starter, Growth, Pro and Enterprise) and during the Freshservice trial. Freshservice has no free plan.
How to get your Freshservice API key
The API key belongs to one Freshservice agent. Allo writes tickets and notes with that API key, and the agent’s role decides what Allo can do: the role must let the agent view and create tickets and view requesters.1
Open your profile settings
In Freshservice, click your profile picture in the top right corner, then click Profile settings.
2
Find Your API Key
The Your API Key section is in the right column of the profile settings.
3
Copy the API key
Copy the API key. You paste the API key into Allo in the next step.
.freshservice.com in your service desk address. For yourcompany.freshservice.com, the domain is yourcompany. Use the freshservice.com address even if your portal uses a custom domain: the Freshservice API only answers on freshservice.com.
Connect in Allo
1
Go to Integrations
In Allo, go to Settings > Integrations.
2
Find Freshservice
Find Freshservice in the Support section and click Connect.
3
Enter your domain and API key
Enter your Freshservice domain in the Freshservice domain field and paste the API key in the API key field.
4
Save and connect
Click Save & Connect. Allo checks the API key with Freshservice and connects the integration.
5
Wait for the contact import
Allo imports your Freshservice requesters and departments. The integration shows the import in progress until the first sync finishes.
Choose your support lines (optional)
Support lines decide which Allo lines send calls and SMS to Freshservice. Only calls and SMS on the selected lines are sent. Calls and SMS on any other line are not sent at all, so sales or personal conversations never reach your service desk. To send every call and SMS, leave the selection on All lines. To choose support lines, go to Settings > Integrations > Freshservice, open Support lines, select the lines and click Save.For an inbound call or SMS, the line is the number the customer dialed or texted. For an outbound call or SMS, the line is the number shown to the customer. Call back or reply from a support line if you want it logged in Freshservice.
Create unknown callers in Freshservice (optional)
The Create unknown callers in Freshservice setting decides what happens when a caller or SMS sender is not a Freshservice requester yet.- On: Allo creates the caller as a new Freshservice requester and logs the call or SMS on that requester. The new requester is named after the Allo contact, or after the phone number if the Allo contact has no name.
- Off: calls and SMS from numbers that are not Freshservice requesters are not sent to Freshservice.
On Freshservice for MSPs, a requester must have an email. Allo cannot create an unknown caller who has no email in Allo, so that call or SMS is not sent to Freshservice.
What syncs
From Freshservice to Allo:- Requesters that have a work or mobile phone number, with their name, primary email, work and mobile numbers, job title and department name
- Departments, with their name, website (from the first domain) and description
- Calls and SMS, logged as private notes on Phone tickets of the matching Freshservice requester
- New requesters, when Create unknown callers in Freshservice is on
+14155551234, (415) 555-1234 or 06 12 34 56 78. Custom phone fields are not checked.
How calls are synced
After each call on a support line, Allo creates a Freshservice ticket for the matching requester, or adds the call to the requester’s recent Allo ticket (see How follow-up calls and SMS are grouped in one ticket). The ticket has:- The type Incident, the source Phone and the priority Low
- The tags
alloandallo-call - A title with the call details, for example
Allo Inbound Call to US Support (+18885550100) - Answered - Leo (2m 03s) - A one-line description:
Phone call with US Support (+18885550100) on Nov 6, 2026, 16:35 UTC (logged by Allo)
- The call direction and result, the start time (UTC), the duration, and the from and to numbers
- The Allo line and the Allo user who handled the call, and the call tags
- The AI summary
- The call transcript, with speaker names when available
- A link to the call recording
Ticket status
Every Allo ticket is Open, for answered calls, missed calls and voicemails alike, so your team sees each phone conversation in its queue. Allo never resolves or closes a ticket: that stays with your agents. Allo creates each ticket as Closed and opens it right away, so Freshservice does not treat it as a new ticket from the requester. If your account makes some fields mandatory to close a ticket, Allo creates the ticket Open directly. Private notes are never emailed to the requester.How follow-up calls and SMS are grouped in one ticket
Calls and SMS with the same requester share one ticket. A new call or SMS joins the requester’s Allo ticket when that ticket is Open or Pending and was last updated less than 1 hour before it. This covers the customer calling or texting again, and your team calling back or replying. When a call or SMS joins an existing ticket:- Allo adds it as a new private note.
- Allo renames the ticket after what it holds:
Allo calls with <requester name> on <line name> (<number>),Allo SMS with …orAllo calls and SMS with …. - Allo adds the
allo-callorallo-smstag if the ticket does not carry it yet. Tags already on the ticket are kept. - The 1-hour window restarts from that call or SMS.
allo-call or allo-sms tag. Allo never adds them to a ticket that came from another channel, such as an email.
Use the allo, allo-call and allo-sms tags to filter Allo tickets in Freshservice views and workflows.
How SMS are synced
After each SMS sent or received on a support line, Allo creates a Freshservice ticket for the matching requester, or adds the SMS to the requester’s recent Allo ticket. The ticket is an Incident with the source Phone (Freshservice has no SMS source), the tagsallo and allo-sms, and a title such as Allo Inbound SMS to US Support (+18885550100) - Leo.
The SMS goes in a private note that contains:
- The SMS direction, the time it was sent (UTC), and the from and to numbers
- The Allo line and the Allo user who sent or received it
- The message text
Click-to-call
Click-to-call is not available for this integration.Troubleshooting
Check the sync status of any call from the call list on web.withallo.com. Each call has an integration indicator showing its sync state.I cannot connect my integration
I cannot connect my integration
Only admins and managers of an Allo workspace can connect integrations. If you don’t see the option, ask your workspace admin or manager to set it up.If Allo rejects your Freshservice details, check these causes:
- The API key is disabled for your agent. Freshservice shows “Your API key is disabled. Please contact your admin to enable it” in Profile settings. Ask your Freshservice account admin to enable the API key, then copy it again.
- The domain is wrong. Enter only the part before
.freshservice.com, for exampleyourcompany, not your custom portal domain. - The API key was regenerated. A new API key replaces the old one. Copy the current API key from Profile settings > Your API Key.
Call or SMS not synced to Freshservice
Call or SMS not synced to Freshservice
Check these causes, in this order:
- The call or SMS was not on a support line. Only calls and SMS on your selected support lines are sent to Freshservice. Check Settings > Integrations > Freshservice > Support lines, or select All lines to send everything.
- The caller is not a Freshservice requester. With Create unknown callers in Freshservice off, calls and SMS from unknown numbers are not sent. Add the phone number to the Freshservice requester, or turn the setting on.
- The caller is a Freshservice agent. Allo matches requesters only. A call from an agent’s number is treated as an unknown caller.
- The phone number is in a custom field. Allo matches on the Work phone and Mobile phone fields only.
- The role of the API key is too narrow. Freshservice refuses requests the role does not allow. Give the agent or integration user a role that can view and create tickets and view requesters.
- The API key stopped working. If the API key was disabled or regenerated, Allo still appears connected but requests fail. Disconnect Freshservice in Allo and connect again with the current API key.
- Freshservice rate limits. Freshservice limits API calls per minute for the whole account (100 per minute on Starter). Nango retries rate-limited requests a few times. If the limit is still reached, the call or SMS is not synced: wait a minute and sync it again from the call list.
A Freshservice requester does not appear in Allo
A Freshservice requester does not appear in Allo
Check these causes:
- The requester has no work or mobile number in Freshservice. Allo only imports requesters with a phone number. Add the number in Freshservice; Allo imports the requester at the next hourly sync.
- The sync has not run yet. Allo checks Freshservice every hour. A requester created or changed in Freshservice appears in Allo after the next sync.
- The first import is still running. On a large Freshservice account, the first import can take several minutes. The integration shows the import in progress until it finishes.
Duplicate requesters
Duplicate requesters
With Create unknown callers in Freshservice on, Allo first looks for an existing Freshservice requester by email, then by phone number, and only creates a requester when it finds none. A duplicate appears when the same person is saved in Freshservice with a different email and a number in a custom phone field. Merge the requesters in Freshservice.
A follow-up call or SMS opened a new ticket
A follow-up call or SMS opened a new ticket
A follow-up call or SMS joins an existing ticket only when all three conditions are true:
- The ticket was created by Allo and still carries the
allo-callorallo-smstag. - The ticket is Open or Pending, not Resolved or Closed.
- The ticket was last updated less than 1 hour before the new call or SMS.
My requester received an email about an Allo ticket
My requester received an email about an Allo ticket
Private notes are never emailed. An email about an Allo ticket comes from your Freshservice notification settings or workflows. Check:
- Workflows in the Workflow Automator that send an email on new or updated tickets. Exclude tickets tagged
allo. - Requester notifications in your Freshservice email notification settings, such as the notifications for new, reopened or closed tickets.
The ticket is unassigned
The ticket is unassigned
Allo assigns the ticket to the Freshservice agent whose email matches the Allo user’s email. If the emails differ, or the agent is deactivated, the ticket stays unassigned. Use the same email in Allo and Freshservice, or assign Allo tickets with a Freshservice workflow on the
allo-call or allo-sms tag.