Choose the architecture before touching a phone number
The phrase “Freshdesk voice AI agent” hides three different jobs:
- Freshcaller: phone numbers, inbound calls, IVR, business-hours actions, and routing.
- Voice provider: conversation, speech recognition, responses, agent instructions, and transfer context.
- Freshdesk: ticket records, notes, follow-up, and the team’s support workflow.
Freshworks’ Voice AI Agent integration guide describes third-party integrations such as Synthflow and Squawkvoice. It also lists speech-enabled IVR separately on the Enterprise plan. Conversational Voice AI and speech-enabled IVR are not interchangeable: one handles a dialogue and can hand over with context; the other primarily routes callers through an IVR experience.
Before changing a number, confirm administrator access to Freshworks, an approved test number, a staffed fallback destination, and a support policy that allows fictional test details. Do not begin with the main customer line. A successful AI greeting proves only that audio connected; it does not prove handover, ticket timing, or post-call automation.
For a general overview of structured support review, 人工智慧資料隱私 is a useful companion, but GlobalGPT content is not Freshworks documentation.
Consumer voice chat is also a different architecture. The ChatGPT 語音功能推出 can help explain conversational interfaces, but it does not supply a Freshcaller number, SIP route, handover context, or Freshdesk ticket.
Install and connect the voice provider
The official Synthflow integration path is designed around a Freshworks Marketplace installation. The current Synthflow Freshworks documentation says to create the account through that flow; an existing standalone Synthflow account cannot be migrated into a Freshworks-connected account.
Step 1: Install the app
In Freshworks, open Admin Settings → Marketplace and Integrations → Marketplace Apps 並搜尋 Synthflow Voice AI Agents (or the supported alternative shown in your account). Install it, then follow the configuration prompts.
Step 2: Use the phone API key
Freshworks and Synthflow both distinguish the phone credential from other API keys. Open the profile or API settings area and find API Details for Phone. Copy that key, not a CRM or Chat key. Enter the Freshworks domain in the app’s configuration form and use its Verify/Save action.
Keep credentials in the authorized configuration form. Do not paste an API key into a team message, a screenshot, or a coding-agent prompt. After saving, use Open Synthflow Portal from the Freshworks app. The linked portal keeps the account association that Freshcaller expects.
Step 3: Create the voice agent
In the linked portal, open My Agents and create the pilot agent. Define a narrow support scope, the approved knowledge, and explicit escalation outcomes. Each new agent receives a SIP URI; Freshcaller keeps the phone number, while the call workflow points to the agent through the provider connection.
The first agent should answer one known question and recognize one human-request path. Avoid a broad “handle anything” instruction. Write down the exact context names the agent will send, because Freshcaller matches those names to actions later.
Build the handover workflow in Freshcaller
Freshworks’ handover call-flow guide treats contexts and actions as separate pieces. A context is a trigger defined in the voice provider, such as billing_escalation 或 caller_requests_human. An action is what Freshcaller does when that context arrives.
開啟 Admin Settings → Configuration and Workflows → Call Workflows, 選擇 Voice AI Agent Handover, name the workflow, and select the voice agent. Enter context names exactly as configured in the provider. Then map each context to a supported action:
設定 If no/unknown context is received to an explicit fallback. Do not leave it implicit. A fallback is part of the product behavior, not an implementation detail: it determines what happens when the AI’s wording and the Freshcaller context list drift apart.
Use the Freshcaller context/action editor as the source of truth for the configured names. A text model can suggest a mapping, but it cannot confirm that the production workflow contains the same spelling.
Map every voice context to an explicit action
billing_escalation
Send a verified billing issue to Billing Support
caller_requests_human
Let the caller choose the right team
after_hours
Capture a message outside business hours
specialist_needed
Apply an existing routing rule
agent_uncertain
Move to a narrower flow
unknown_context
Fail safely when the context is missing
Assign the workflow to a test number
Creating a handover flow does not activate it on a number. In Freshcaller, go to Admin Settings → Channels → Phone, select an approved number, and open its edit controls. Under Call Actions:
- Choose the business-hours schedule.
- 設定 Action During Business Hours 至 Send to Voice AI Agent.
- Select the intended voice agent and the exact handover workflow.
- Review the outgoing-call action and save.
Test once during business hours and once outside them. Verify the actual destination and the handoff summary in the receiving agent view. Do not rely on the voice agent saying “I’m transferring you.” The Freshcaller handover documentation says the receiving agent should see a brief summary, with the detailed handoff context and later conversation, transcript, and recording available in the Inbox when supported by the configuration.
Understand Freshcaller and voice-provider billing
Freshcaller and the voice provider meter different things. Freshworks’ current Freshcaller pricing page shows annual seat prices plus pay-per-minute charges:
| 計劃 | Annual seat price | Included incoming minutes per account/month | Notable voice features |
|---|---|---|---|
| 免費 | $0/agent/month | No allowance listed | Basic caller ID, notes, greetings, metrics |
| Growth | $15/agent/month | 2,000 | Number porting, wait queues, voicemail, transfers, recording |
| 專業 | $39/agent/month | 3,000 | Routing automation, conferencing, smart escalations |
| 企業 | $69/agent/month | 5,000 | Speech-enabled IVR and service-level monitoring |
Freshworks says Freshcaller charges for the full time the phone line remains active, including the human-agent portion after an AI handoff. The voice provider charges its own AI-handled duration according to its plan. For a ten-minute call with six minutes handled by the AI and four minutes handled by a human, Freshcaller can meter all ten minutes while the provider meters six. A seat price alone is therefore not a complete call-cost estimate.
Provider plans and capacity can change. Keep the Freshcaller table separate from Synthflow’s account-specific terms, and check both sources on the date you publish. For general plan-comparison context, 多功能 AI 工具與平台 can be linked, but it does not replace either vendor’s pricing page.
Verify the Freshdesk ticket path separately
The phone route and the ticket route can fail at different times. A provider may create a Freshdesk ticket as soon as the call starts, then add its summary later. An automation triggered by “new ticket” may run before the useful call context exists. An automation triggered by “ticket update” may run repeatedly as the provider adds notes.
For the post-call layer, automatic support-conversation summaries offers a useful review framework. It is not evidence that Freshcaller created or updated the ticket in this setup.
Use an authorized fictional test call, then inspect the resulting ticket manually:
| 舞台 | 需核實的事項 |
|---|---|
| Voice handoff | The call reached the intended human queue or documented fallback |
| Ticket creation | A Freshdesk ticket exists with expected call context |
| Context quality | Identity status, request, and unresolved facts remain explicit |
| Automation scope | Only the pilot ticket was handled |
| Draft destination | The follow-up appears as a private internal note |
| Customer reply | Sending remains disabled until separately approved |
Only after the ticket shape is known should you configure a narrow Freshdesk automation. Keep Send ticket reply disabled. Require approval for Leave internal note, and leave unrelated actions off. Distinguish a new-ticket trigger from a ticket-update trigger, and create a fresh matching test event after the automation exists. Do not expect a newly created rule to process an earlier inspection ticket retroactively.
When selecting a separate text-review model, compare the actual rubric rather than a familiar brand name. A tested AI assistant comparison can inform that choice, but the Freshcaller route still needs its own authorized call test.
A safe fictional post-call review prompt
The following is a text-review prompt for GlobalGPT, not a Freshdesk API command. It deliberately keeps customer replies and ticket writes out of scope:
The model’s output is useful only as a draft to inspect. It does not prove that Freshcaller transferred the call, that Freshdesk created a ticket, or that the private note was posted. For a broader automation perspective, 如何使用 ChatGPT 代理 provides context, but it is not a Freshworks control surface.
For shared review work, an all-in-one AI tool for teams can centralize draft comparisons. A separate 全功能 AI 模型概覽 helps explain model choice; neither can verify the phone transfer.
Troubleshooting before expanding the pilot
Six checks before expanding the pilot
The voice agent is missing from the Freshcaller dropdown.
The API key fails verification.
The call reaches the wrong team.
The ticket has no final summary.
Private notes duplicate.
The cost estimate is too low.
總結
The dependable Freshdesk voice AI setup is a staged handoff: Freshcaller owns the number and route, the provider owns the conversation, and Freshdesk owns the ticket and follow-up. Install through the supported Marketplace path, use the phone API key, map exact contexts to explicit actions, assign the workflow to a test number, and inspect the ticket before enabling any reply automation. Use GlobalGPT for fictional text review, not as evidence that a phone transfer or Freshdesk write occurred.
Review a fictional post-call checklist in GlobalGPT before your next authorized Freshcaller test.
常見問題
Is Freshdesk the phone system in this setup?
No. Freshcaller carries the phone number, IVR, and call routing. Freshdesk is where ticket context and follow-up work are reviewed.
Can I use an existing standalone Synthflow account?
Synthflow’s Freshworks integration documentation says the account must be created through the Freshworks Marketplace flow. Standalone-account migration is not supported.
Which API key does the integration need?
Use the Freshcaller key in the **API Details for Phone** section, not the CRM or Chat key. Enter the Freshworks domain in the integration form.
How does Voice AI Agent Handover decide where to send a call?
The provider sends a configured context. Freshcaller matches it to an action such as a queue, IVR, voicemail, another agent, routing automation, or hangup, with a fallback for unknown context.
Does Freshcaller keep charging after an AI handoff?
Freshworks says Freshcaller charges for the entire time the phone line remains active, including the human-agent portion. The voice provider bills its own AI-handled duration separately.
Will every completed call create a complete Freshdesk ticket?
Do not assume that. Verify when the ticket is created, which fields and notes arrive, and when the final summary or recording becomes available.
