Worked Example: A FreshDesk Support Agent

Worked Example: A FreshDesk Support Agent

Applies to: AGS 1.0  |  Level: Beginner  |  Reading time: 3 min
Part of: Using Tools with Your Agent (Overview)  |  Last reviewed: 25 Sep 2026

This example walks through a complete FreshDesk setup, from install to a live call, so you can see how every article in this section fits together. Use it as a model for any vendor.

What you'll learn

  • How a finished vendor-tool setup looks, at a glance
  • What a well-instructed agent sounds like on a real call
  • The four-step pattern to reuse for any vendor: identify → confirm → act → report back

The setup at a glance

ItemDetail
GoalThe agent identifies the caller, logs their issue and reads back a ticket number
PathVendor tool. FreshDesk is already in the Tool Catalog (Installing a Vendor Tool)
ConnectionOne FreshDesk connection for this customer
Tools installedGetContactById, CreateContact, CreateTicket, AddNoteToTicket
Install variablesbaseUrl: this customer's FreshDesk domain, entered once per tool at install time
Attached toThe customer-service agent (Attaching Tools to Your Agent)

What the call sounds like

Tool calls are shown as calls ToolName. The caller doesn't hear them.

Caller: Hi, my office internet has been dropping all morning.

Agent: I'm sorry about that. Can I take your name and email so I can pull up your account?

Caller: Maria Santos, m-santos at northgate dot com.

Agent: That's M, dash, S, A, N, T, O, S, at northgate dot com. Is that correct?

Caller: Yes.

calls GetContactById

Agent: Thanks, Maria, I have you here. I'll log this as "intermittent internet dropouts since this morning". Does that cover it?

Caller: Yes, that's it.

calls CreateTicket

Agent: That's ticket four-four-seven-one. A technician will call you within the hour.

What's happening behind the scenes

Pattern stepWhat the agent does
1. IdentifyCollects the caller's name and email before calling any tool, as the prompt instructs.
2. ConfirmSpells the email back and confirms the issue description before acting on either.
3. ActCalls GetContactById to look the caller up instead of guessing, then calls CreateTicket only after the description is confirmed.
4. Report backReads the ticket number digit by digit and sets a clear expectation for what happens next.

Why the other two tools are installed

  • CreateContact: used if the lookup finds no match, so a new caller can still get a ticket. Not triggered in this call.
  • AddNoteToTicket: leaves extra context for the technician on an existing ticket. Not triggered in this call.
✔ Reuse this pattern for any vendor: identify → confirm → act → report back. Write each step into the tool's prompt block, as shown in Attaching Tools to Your Agent.

Build it yourself

  1. Install the FreshDesk tools with one connection for the customer, and fill in baseUrl.
  2. Attach the tools to your agent and add a prompt block for each one.
  3. Test and deploy the change before any real caller reaches it.