Helpdesk

Assign a ticket to a team member (they get a notification), or unassign it by omitting the assignee.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/helpdesk.assign \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool helpdesk_assign at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a help desk ticket on the customer's behalf. Stamps a first-response SLA deadline from the account's per-priority policy, links (or creates) the CRM contact from the requester's email/phone, and notifies the assignee — or the desk's default assignee, or the whole account. Sends no email or SMS to the customer (the 'we got your request' confirmation email goes out only for the customer's own public-portal submissions).

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/helpdesk.create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "subject": "Example",
    "body": "example"
  }'

Over MCP the same operation is the tool helpdesk_create at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one help desk ticket by id, with its full thread — public replies the customer can see and internal agent-only notes, each marked by its `internal` flag.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/helpdesk.get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool helpdesk_get at https://app.chirply.io/api/mcp, same bearer token, same input.

Read the account's help desk configuration: the first-response SLA target in minutes for each ticket priority, whether the customer-facing submission portal is on and the public URL it is served at, the portal's display name and intro copy, the default assignee and default queue new tickets land in, and whether public replies are also emailed to the customer. Reads only — nothing is changed and nobody is contacted.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/helpdesk.get_settings \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool helpdesk_get_settings at https://app.chirply.io/api/mcp, same bearer token, same input.

List the account's help desk tickets (support requests from its OWN customers), most recently updated first. Optionally filter by status, priority, assignee, queue, or the linked contact.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/helpdesk.list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25,
    "offset": 0
  }'

Over MCP the same operation is the tool helpdesk_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Post an agent message on a ticket. A public reply (internal=false) is shown to the customer on their ticket status page, stops the first-response SLA clock, and moves a new/open ticket to 'waiting' — and when the account's help desk email updates are on (the default while an email provider is connected) and the ticket has a requester email, the reply is ALSO emailed to that real customer through its own connected email account, with a reply-to address that threads their answer back onto the ticket. It is outward-facing customer communication. An internal note (internal=true) stays agent-only and is never emailed.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/helpdesk.reply \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "body": "example"
  }'

Over MCP the same operation is the tool helpdesk_reply at https://app.chirply.io/api/mcp, same bearer token, same input.

Change a ticket's priority. While the first-response SLA clock is still running, the deadline is recomputed under the new priority's target.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/helpdesk.set_priority \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "priority": "low"
  }'

Over MCP the same operation is the tool helpdesk_set_priority at https://app.chirply.io/api/mcp, same bearer token, same input.

Move a ticket between statuses. Setting 'solved' stamps the solve time and makes the customer's ticket page offer a one-time 1–5 CSAT rating; reopening a solved/closed ticket clears the solve stamp. Reversible at any time.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/helpdesk.set_status \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "status": "new"
  }'

Over MCP the same operation is the tool helpdesk_set_status at https://app.chirply.io/api/mcp, same bearer token, same input.

Change the account's help desk configuration. Omitted fields are left alone. Turning `portal_enabled` on PUBLISHES a public web page where anyone with the link can open tickets against this account, and the portal name/intro appear on that public page; changing the default assignee or queue changes where every new customer ticket lands; the SLA minutes set the first-response deadline stamped on tickets from now on (existing tickets keep their deadline); `email_updates` controls whether public replies are also emailed to the real customer through the account's own connected email. Requires the plan that includes the help desk. Returns the settings as they now stand.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/helpdesk.update_settings \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "sla_urgent_minutes": 5,
    "sla_high_minutes": 5
  }'

Over MCP the same operation is the tool helpdesk_update_settings at https://app.chirply.io/api/mcp, same bearer token, same input.