AI Add-on — $1,999/yr flat
Ticket drafter, duplicate finder, status explainer, auto-classification — stacks on any band.
Salesforce ↔ Jira Connector
Escalate and track Jira issues without leaving a Case
A standalone Salesforce package that lets support agents escalate a Case straight to Jira, track live status in a Case panel, and send agent-curated comments back — with a full audit trail. Works with or without the AItocha CX platform.
Book a Scoping CallPricing
| Salesforce users | Annual | Effective $/user/mo |
|---|---|---|
| 1–10 | $1,299 | ~$10.83 |
| 11–25 | $2,199 | ~$7.33–$8.80 |
| 26–50 | $3,499 | ~$5.83–$6.99 |
| 51–100 | $5,499 | ~$4.58–$5.50 |
| 101–200 | $6,999 | ~$2.92–$3.50 |
| 201+ | Custom (Enterprise) | — |
Add-ons
Additional project/instance — $1,499/yr each
Map another Jira project or a second Salesforce org beyond the first.
Enterprise / unlimited — From ~$12,000–$15,000/yr
No object/instance restriction, priority support — custom quote for 201+ seats.
Frequently Asked Questions
What do we need to provide before setup can start?
A Jira Cloud API token from your own Jira instance, generated by your Jira admin — the connector authenticates as a service account using it, so we can't create or link anything in your Jira until you provide one. Your Salesforce org also needs outbound network access to Jira's API, which is the default for most orgs unless outbound traffic is restricted by firewall or proxy policy. We'll walk you through generating the token during setup, on any delivery path.
Does every agent need their own Jira license?
No. Salesforce talks to Jira through one shared service-account connection (Named Credential + External Credential) — there's no per-seat Atlassian license to buy. Our price bands are based on how many Salesforce users have the connector's permission set assigned, not Jira licenses.
Does everything written on a Case get forwarded to Jira automatically?
No. Outbound is agent-curated only. The agent composes exactly what engineering sees and sends it deliberately, attributed to them — nothing on the Case (emails, chat transcripts, other comments) is bulk-forwarded.
Can an agent pull up any Jira ticket, even outside their team's project?
No. Access is controlled in three layers: the Jira service account itself is scoped only to approved projects (the real boundary), the Salesforce Case panel only shows issues linked to that Case, and an optional project allowlist restricts search even if the service account is ever over-permissioned.
What's the difference between White-glove, Guided Setup, and Self-install?
White-glove ($3,499 one-time): we deploy and configure it in your org. Guided Setup ($1,499 one-time): your admin installs it while we walk through configuration live on a call. Self-install ($0 setup): an unattended managed-package install with an in-app wizard — this is on our roadmap, not yet shipped.
Do we have to buy the AI add-on to use the connector?
No, it's optional. The base connector (escalate, track, agent-curated comments, audit ledger) is fully functional on its own. The AI add-on ($1,999/yr flat) layers on a ticket drafter, duplicate-issue finder, and auto-classification — AI only ever drafts, an agent always sends.
What if we need to turn it off?
Three kill switches — whole connector, outbound sync, inbound sync — allow immediate shutoff without a deploy. Unlinking a Case from a Jira issue preserves the audit history rather than deleting it.