🎧Support
The 3 support skills: instant answers to common Dapta questions, opening a tracked ticket, and retrieving your support history.
These skills handle help and escalation, from instant FAQ answers to filing and tracking tickets.
customer-support
What it does: Answers common Dapta questions instantly: how to cancel, update payment, reset access via OTP, invite team members, find support contacts and hours, plus credit and pricing facts and the referral program, with direct links into the app. Knowledge-only: it answers and navigates, it does not change anything in your account.
Use it when: You have a how-do-I or where-do-I account, billing, or contact question, want pricing or credit-cost facts, need the support email or chat widget location, or want to know about Refer & Earn.
Try saying:
"How do I cancel my subscription?"
"How many credits does a voice call use?"
"How do I contact support and what are your hours?"
You get back: A direct, plain-language answer with the exact app link or contact channel, the relevant policy, and pricing facts.
Writes data? No. Knowledge-only, makes no tool calls and cannot modify your account. For a tracked case, it hands off to create_support_ticket.
Behind the scenes: no tools. Answers come from the skill's built-in FAQ, policies, and navigation links.
create_support_ticket
What it does: Opens a tracked support ticket with Dapta's team when you need human help or want a case on record. It always shows you a preview of the ticket first and only files it after you confirm.
Use it when: You are blocked (access, billing, technical, or security), the answer is not covered by the FAQ or docs, or you explicitly want to escalate.
Try saying:
"Open a support ticket, my voice agent won't place outbound calls."
"I need to escalate this to a human."
"File a case about my billing issue."
You get back: A preview of the ticket (title, product area, issue type, body) to confirm; after you say yes, a ticket card with its number, state, area, category, assignee, and creation time, plus a note that an advisor will follow up. If a matching open ticket already exists, it tells you instead of creating a duplicate.
Writes data? Yes, via preview then commit. Shows the ticket before filing, commits only after you confirm.
Behind the scenes: preview_create_ticket, then commit_create_ticket, then get_ticket_card to display the result.
support-history
What it does: Retrieves and displays your support history: your own past tickets and conversations, your team's ticket activity, distribution stats, and the full detail of any single ticket.
Use it when: You want to know whether you have open tickets, review past cases, see what tickets your team has open, or pull up one specific ticket.
Try saying:
"Do I have any open support tickets?"
"Show me my support history."
"What tickets does my team have open?"
You get back: A clean list of your conversations and tickets (title, state, date), distribution counts by state or type, a workspace-wide roll-up, or a single detailed ticket card. If there is nothing, it tells you so.
Writes data? No, read-only. To open a new ticket it routes you to create_support_ticket.
Behind the scenes: list_tickets_by_email, get_ticket_distribution_by_email, list_tickets_by_workspace, get_ticket_card.
Last updated