# Sippet AI ## Docs - [HTTP RPC API overview](https://sippet.ai/docs/api-reference/introduction.md): How to call Sippet's org API directly over the public RPC transport. - [Run a public RPC action](https://sippet.ai/docs/api-reference/public-rpc/run-a-public-rpc-action.md): Execute a public org RPC action by sending the action name and payload in the request body. - [Validate a public RPC action payload](https://sippet.ai/docs/api-reference/public-rpc/validate-a-public-rpc-action-payload.md): Validate an action payload before execution. Use the same action name and payload shape as `/rpc/public/run`. - [No-code AI agents](https://sippet.ai/docs/console/ai-agents.md): Configure support agents with prompts, tools, files, channels, and escalation behavior without writing application code. - [Create an AI agent for support and escalation](https://sippet.ai/docs/console/ai-agents-guide.md): Build a no-code agent that answers product questions, uses connected knowledge, and hands off when needed. - [AI providers (BYOK)](https://sippet.ai/docs/console/ai-providers.md): Connect your own provider credentials for voice and AI agent behavior. - [Connect and validate a BYOK provider](https://sippet.ai/docs/console/ai-providers-guide.md): Add an OpenAI or Gemini key and confirm it is ready for production support workflows. - [API keys](https://sippet.ai/docs/console/api-keys.md): Create and manage secret or publishable keys for controlled integration access. - [Call center](https://sippet.ai/docs/console/call-center.md): Run live voice support with operators, AI agents, queues, transcripts, and assist controls. - [Set up a basic call workflow](https://sippet.ai/docs/console/call-center-guide.md): Configure a simple inbound and outbound call flow with AI agent routing and operator coverage. - [Conversations & memory](https://sippet.ai/docs/console/conversations-memory.md): Keep support context alive across channels with shared conversation history and contact memory. - [Use shared memory to improve follow-up](https://sippet.ai/docs/console/conversations-memory-guide.md): Keep contact context consistent across voice, email, and messaging so your team and agents can follow through. - [Core Features](https://sippet.ai/docs/console/core-features.md): Understand Sippet's core product model, including live vs sandbox mode and the main workflows the console supports. - [Custom mailbox](https://sippet.ai/docs/console/custom-mailbox.md): Connect branded mailboxes and outbound identities so email support runs through your own domain. - [Connect a branded support mailbox](https://sippet.ai/docs/console/custom-mailbox-guide.md): Set up an inbound mailbox and outbound identities for AI-assisted or team-managed email support. - [Custom SIP trunking](https://sippet.ai/docs/console/custom-sip-trunking.md): Bring your own telephony stack into Sippet with gateways, numbers, and SIP user workflows. - [Connect a custom SIP trunk](https://sippet.ai/docs/console/custom-sip-trunking-guide.md): Add a gateway, connect a number, and route calls into AI-agent or operator workflows. - [Discord + GitHub workflow](https://sippet.ai/docs/console/discord-github-workflow.md): Use Discord support intake plus GitHub knowledge to answer product questions and escalate likely bugs. - [Discord integration](https://sippet.ai/docs/console/discord-integration.md): Watch product-support channels, capture questions, and let AI agents respond with shared context. - [Set up Discord support monitoring and replies](https://sippet.ai/docs/console/discord-integration-guide.md): Connect Discord, bind support channels, assign an AI agent, and review examples before scaling replies. - [Email](https://sippet.ai/docs/console/email.md): Connect branded mailboxes, sender identities, and inbound handling for email-based support. - [Connect a mailbox and route support email](https://sippet.ai/docs/console/email-guide.md): Set up a mailbox, attach identities, and route inbound email into Sippet support workflows. - [GitHub integration](https://sippet.ai/docs/console/github-integration.md): Connect repositories to AI agents so support workflows can use live issue and codebase knowledge. - [Connect GitHub knowledge to an AI agent](https://sippet.ai/docs/console/github-integration-guide.md): Install the GitHub app, bind repositories, and attach them to an AI agent for product-aware support. - [Integrations](https://sippet.ai/docs/console/integrations.md): Connect Sippet to the external channels and systems your support team already uses. - [Playbooks](https://sippet.ai/docs/console/playbooks.md): Automate follow-up, callbacks, and repeated support operations with scheduled or triggered runs. - [Build a follow-up or callback playbook](https://sippet.ai/docs/console/playbooks-guide.md): Create a repeatable automation flow for post-call follow-up, reminders, or callback scheduling. - [SMS & WhatsApp](https://sippet.ai/docs/console/sms-whatsapp.md): Support customers over outbound messaging with shared contact context and AI-assisted follow-up. - [Configure messaging and follow up across channels](https://sippet.ai/docs/console/sms-whatsapp-guide.md): Set up messaging and use it to continue a support conversation after voice or email. - [Team members](https://sippet.ai/docs/console/team-members.md): Invite operators and admins, assign roles, and manage who can configure or run support workflows. - [Invite and assign team roles](https://sippet.ai/docs/console/team-members-guide.md): Bring operators and admins into the org with the right role boundaries from the start. - [Templates](https://sippet.ai/docs/console/templates.md): Create reusable content for email, SMS, and API-style support follow-up workflows. - [Create reusable templates](https://sippet.ai/docs/console/templates-guide.md): Build reusable email, SMS, and API request templates for support and follow-up workflows. - [Verification](https://sippet.ai/docs/console/verification.md): Complete org, phone, and email verification steps needed for trusted outbound and support workflows. - [Complete org verification](https://sippet.ai/docs/console/verification-guide.md): Submit the main verification information for your org and confirm email and phone ownership. - [Webhooks](https://sippet.ai/docs/console/webhooks.md): Send Sippet events to your own backend so external systems can react to support activity. - [Subscribe your backend to Sippet events](https://sippet.ai/docs/console/webhooks-guide.md): Create a webhook endpoint and use it to react to support activity outside the Sippet console. - [Production readiness](https://sippet.ai/docs/development.md): Best practices for launching and operating Sippet integrations. - [Getting started (classic)](https://sippet.ai/docs/guides/getting-started-classic.md): Build a realtime telephony experience using short-lived session tokens. - [Realtime session tokens](https://sippet.ai/docs/guides/realtime-session-tokens.md): Secure your browser realtime subscriptions with short-lived session tokens. - [Realtime telephony patterns](https://sippet.ai/docs/guides/realtime-telephony-patterns.md): Use Sippet realtime events to keep your call UI synchronized. - [Sippet AI Console](https://sippet.ai/docs/index.md): Docs for omni-channel AI support, triage, and operator workflows in Sippet. - [Quickstart](https://sippet.ai/docs/quickstart.md): Build your first secure realtime telephony flow with Sippet. - [Frontend realtime SDK](https://sippet.ai/docs/sdk-js/introduction.md): Use @sippet-ai/sdk-js in your frontend for browser calling, sockets, and live call events. - [HTTP RPC reference](https://sippet.ai/docs/sdk-js/rpc-actions.md): Public HTTP RPC transport and full function, input, output, and field-selection types. ## OpenAPI Specs - [openapi](https://sippet.ai/docs/api-reference/openapi.json) ## Optional - [Website](https://sippet.ai) - [Console](https://console.sippet.ai) - [Contact Sales](https://sippet.ai/contact)