# GoPimi > GoPimi is an API-first ticket management platform with a unified inbox. It offers 157 REST API endpoints, webhooks with 15 event types, an email-to-ticket pipeline, multi-workspace isolation, and inbound email automations. Every operation in the UI is available as an API call, making the platform fully automatable. GoPimi ships three workflows — Tickets (structured support with SLA), Shared Inbox (team conversations), and Personal Inbox (private per-user email). Pricing starts at $9/month (Lite), $29/month (Pro), and $79/month (Business), with a 14-day free trial on every plan. ## Documentation - [Documentation Hub](https://gopimi.com/docs/): Index of all guides and API reference. - [API Reference](https://gopimi.com/docs/api-reference/): Interactive OpenAPI 3.1 docs for all 157 REST endpoints, powered by Scalar. - [Getting Started](https://gopimi.com/docs/getting-started/): Sign-up-to-first-ticket walkthrough covering account creation, workspace setup, email configuration, and receiving the first inbound email. ## Guides - [Email Pipeline](https://gopimi.com/docs/guides/email-pipeline/): Inbound and outbound email flow, Mailgun integration, forwarding addresses, purpose-based routing (ticket vs inbox), threading via Message-ID and In-Reply-To headers, and attachments. - [Inbound Email Automations](https://gopimi.com/docs/guides/automations/): Trigger-action rules that run on ticket_created and conversation_created events. Match on from_email (equals/domain), subject_contains, body_contains. Actions: add_tag, assign_agent, send_response (auto-reply with template variables and 60-minute per-recipient cooldown). - [Webhooks](https://gopimi.com/docs/guides/webhooks/): 15 event types, HMAC-SHA256 signed payloads, exponential-backoff retry, and delivery logs with status and response code. - [Workspaces & Teams](https://gopimi.com/docs/guides/workspaces/): Multi-workspace isolation model, owner and member roles, invitation flow, and per-plan resource quotas. - [Contacts & Custom Fields](https://gopimi.com/docs/guides/contacts/): Contact and organization management, plus 7 custom field types (text, number, date, select, boolean, url, email). - [SLA Policies](https://gopimi.com/docs/guides/sla/): First-response and resolution deadlines, breach detection, and notification delivery. - [WordPress Plugin](https://gopimi.com/docs/guides/wordpress/): Install and configure the GoPimi plugin for WordPress email delivery and embedded ticket forms. ## Blog - [Support Ticket Management: What It Is and Why It Matters](https://gopimi.com/blog/support-ticket-management/): Introduction to ticket management as a discipline — what a ticket represents, why queuing matters, and how modern systems handle status, assignment, and SLA. - [Why Your Team Needs a Unified Inbox for Support](https://gopimi.com/blog/unified-inbox-for-teams/): Case for collapsing shared email addresses into one collaborative inbox, the difference between shared inbox and ticketing, and when each is appropriate. - [How to Integrate a Helpdesk API Into Your Product](https://gopimi.com/blog/helpdesk-api-integration/): Practical guide to integrating a REST helpdesk API into a product backend — authentication, creating tickets from events, syncing contacts, and using webhooks. - [How Email-to-Ticket Automation Works](https://gopimi.com/blog/email-to-ticket-automation/): Step-by-step of the email-to-ticket pipeline — MX records, Mailgun webhook processing, threading by Message-ID, and routing by purpose. - [How to Automate Support Tickets with AI Agents](https://gopimi.com/blog/ai-agent-helpdesk-automation/): Patterns for letting AI agents triage, tag, and respond to tickets using GoPimi's REST API and webhooks. - [Why API-First Helpdesk Over AI Chat](https://gopimi.com/blog/api-helpdesk-over-ai-chat/): Comparison between API-first ticket management and AI-chat-first helpdesks, including control, auditability, and integration depth. ## Use Cases - [Use Cases Overview](https://gopimi.com/use-cases/): Industry and team-size scenarios. - [SaaS Teams](https://gopimi.com/use-cases/saas/): Running customer support for a software-as-a-service product with per-customer workspaces and webhook-driven automations. - [Dev Agencies](https://gopimi.com/use-cases/agencies/): Multi-client support with isolated workspaces, custom email domains per client, and shared team access. - [Solo Developers](https://gopimi.com/use-cases/solo-developers/): Single-person operations using the personal inbox, canned responses, and lightweight automation. ## Product - [Homepage](https://gopimi.com/): Product overview, core philosophy (API-first, everything automated), feature highlights, pricing, FAQ. - [Changelog](https://gopimi.com/changelog/): Release history with CalVer versioning (YY.M.DD). - [WordPress Plugin Landing](https://gopimi.com/wordpress-plugin/): Standalone page for the WordPress plugin. ## Compare - [GoPimi vs Zendesk](https://gopimi.com/gopimi-vs-zendesk/): API-first ticket management compared to Zendesk — pricing, REST API depth, webhooks, workflows, and OpenAPI coverage. - [GoPimi vs Freshdesk](https://gopimi.com/gopimi-vs-freshdesk/): API-first ticket management compared to Freshdesk — pricing, REST API depth, authentication, and free-plan positioning. - [GoPimi vs Help Scout](https://gopimi.com/gopimi-vs-help-scout/): API-first ticket management compared to Help Scout — pricing, API depth, shared inbox vs multi-workflow, and knowledge-base positioning. ## Optional - [FAQ](https://gopimi.com/faq/): 34 questions across 7 categories covering setup, billing, email, API, security, and integrations. - [Privacy Policy](https://gopimi.com/privacy-policy/): Data handling, third-party processors, and GDPR posture. - [Terms of Service](https://gopimi.com/terms/): Legal terms governing use of the platform.