Customer support

What Customer Support Is For

Use the Cofounder MCP to select a support inbox, read customer requests, organize tickets, and share internal notes. Every company member can use these tools. To contact the Cofounder team, use support_create.

The examples below show MCP tool arguments. Include company_id for a personal connection; a company connection already selects its company.

Select Your Inbox

Call customer_support_inbox_create to create and select a mailbox:

{"source": "new", "local_part": "support"}

Set mail_domain to a domain the company owns, or mail_domain_id to a verified mail domain. Pending domain setup leaves support unconfigured; repeat the call after completing the returned steps. Trial-domain inboxes and the first owned-domain inbox are free; additional owned-domain inboxes cost $2/month.

To select an existing company-owned mailbox, call the same tool with:

{"source": "existing", "inbox_resource_id": "<mailbox-id>"}

Read the selected inbox with customer_support_settings_get. Setup creates missing support/policies.md in the Library and preserves existing policies. It does not select another inbox automatically, enable automatic replies, or run investigations. Inbox replacement is not available yet.

Read Incoming Requests

New customer email creates an open ticket linked to the sender's CRM contact. Replies stay on the same ticket. Email sent to other inboxes does not create support tickets.

Call customer_support_tickets_list with status set to open to find outstanding requests. Open a ticket with customer_support_tickets_get:

{"ticket_id": "<ticket-id>", "include_messages": true}

Pass attachment_ids as a list of IDs from those messages to get download links. Leave include_messages and attachment_ids out to read local ticket details without contacting the mailbox provider. Continue a list or message page by passing its next_cursor as cursor.

Organize Tickets

Call customer_support_tickets_update to change a ticket's status:

{"ticket_id": "<ticket-id>", "status": "closed"}

Statuses are open, waiting_customer, waiting_company, and closed. Set priority to urgent, high, normal (the default), or low. Use assignee_user_id for the responsible teammate, next_action for the internal next step, and needs_human_attention for work needing a person's decision.

Omitted fields stay unchanged. Set assignee_user_id or next_action to null to clear it. The next action can contain up to 100,000 characters. Assignment changes responsibility; every member retains access. Human attention changes neither assignment nor automation. Filter tickets by status, priority, assignee_user_id, or needs_human_attention in customer_support_tickets_list.

Updates send no email. A customer reply reopens a closed ticket and preserves its management fields and notes.

Share Internal Notes

Call customer_support_notes_create with ticket_id and body. Each note can contain up to 100,000 characters. Notes record the authenticated member and creation time. They remain if the author deletes their account. Read them oldest first with customer_support_notes_list; pass next_cursor as cursor to continue. Notes stay internal and send no email.

cofounder customer-support notes create --ticket-id <ticket-id> --body "Check the refund with a teammate."
cofounder customer-support notes list --ticket-id <ticket-id>

CLI And API Equivalents