Support
Last Updated: 2025-12-02 10:22 UTC
Personas: All
What you'll learn
- Contact Plixo support using the right channel for urgency.
- File actionable tickets with the necessary context.
- Monitor system status and uptime.
Step-by-step
- Choose the right contact option.
- Start with the in-app Support hub (
/support). The docs CTA, Grok-powered chatbot, and structured request form live there. - File requests directly in the Support form so the team gets org/user context, impact, and any links you include.
- For P1 payment incidents (payments blocked), call the emergency line listed in your onboarding packet for 24/7 escalation.
- Start with the in-app Support hub (
- File high-quality tickets.
- Include organization name, invoice or request ID, page URL, description, and expected outcome.
- Attach screenshots or screen recordings when possible. Redact sensitive data if sharing externally.
- Monitor status and uptime.
- Visit status.plixo.ai for real-time incident updates and history.
- Subscribe to SMS or email alerts for components you rely on (mini-portal, Stripe syncs, email delivery).
Success checks
- Tickets receive faster resolutions because Support has the full context.
- Urgent issues reach the emergency line quickly, minimizing downtime.
- Teams proactively monitor the status page instead of waiting for alerts.
Common pitfalls
- Submitting vague tickets. Provide replication steps to reduce back-and-forth.
- Bypassing the Support hub. Emailing individuals delays response because the ticket lacks org context.
- Escalating non-critical issues via the emergency line. Reserve it for payment-blocking incidents only.
- Ignoring status subscriptions. Opt-in to alerts so you know about incidents immediately.