Quickstart

Get a working support queue live in about ten minutes — a connected mailbox, a verified domain, your team, and a first ticket flowing end to end.

This guide gets a working support queue live in about ten minutes: a connected mailbox, a verified sending domain, your team invited, and a first ticket flowing end to end. You can do every step from the dashboard — the API calls below are optional, for teams that prefer to script setup.

1. Create your workspace

   Sign up and name your workspace. You’ll get an isolated subdomain like acme.cherryrise.app immediately — every workspace is multi-tenant isolated by default.

2. Connect your support mailbox

   Forward [email protected] to the address Cherryrise gives you, or connect over IMAP. New mail becomes a ticket the moment it arrives.

   bashCopy

   # Forward your support address to your workspace inbox
   [email protected]  →  [email protected]
   
   # Or connect a mailbox over IMAP from Settings → Channels

3. Verify your sending domain

   Publish two DNS records so replies are signed as your own domain via BYODKIM — no “via” leak. Add the records, then click Verify; propagation is usually under a minute.

   dnsCopy

   TXT    cr._domainkey.acme.com    v=DKIM1; k=rsa; p=MIIBIjANBg...
   CNAME  mail.acme.com              feedback-smtp.us-east-1.amazonses.com

   New to these records? See DKIM explained and the deliverability guide.

4. Invite your team

   Add agents and assign roles. Use RBAC to scope contractors to assigned-only visibility — enforced server-side, not just hidden in the UI.

5. Send a test ticket

   Email your support address from a personal account and watch it land in the queue. Reply from Cherryrise; the customer receives it from your domain. To create a ticket programmatically instead:

   bashCopy

   curl https://api.cherryrise.com/v1/tickets \
     -H "Authorization: Bearer $CHERRYRISE_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "subject": "My first ticket",
       "requester": { "email": "[email protected]" },
       "message": "Hello from the API"
     }'

Where to go next

You’ve got a live queue. From here, most teams set up routing and SLAs, then wire in the tools they already use:

• Build your first routing rule and SLA policy (with business hours).
• Turn on a macro or two for your most common replies.
• Connect Slack, Linear or Shopify.
• Explore the full API reference to script the rest.