Skip to content

Contact Support ​

You can solve most issues by talking to your bot directly or checking the help guides. But when you need a human, here's how to reach us — and how fast we respond.

Before You Contact Support ​

Try these first — they're faster than a ticket:

  1. Ask your bot. Tell it what's wrong: "You're not responding to customers" or "Email isn't working." It can often diagnose and fix issues on its own.
  2. Check the troubleshooting guide. Our symptom-first checklist covers the most common issues. See Troubleshooting.
  3. Browse the FAQ. Quick answers to the questions owners ask most. See FAQ.

How to Open a Support Ticket ​

  1. Log in to your portal at app.agente.systems.
  2. Click Help → Open a Ticket (or the ? icon in the bottom corner).
  3. Fill in:
    • What's happening — describe the issue in plain language.
    • When it started — approximate date and time.
    • Which channel — email, WhatsApp, widget, or the bot itself.
    • Screenshots — if you have them, attach them.
  4. Submit. You'll get a confirmation with a ticket number.

You can also email support@agente.systems directly — it creates a ticket automatically.

Response Times ​

TierPriceResponse Time
Associate$299/moWithin 24 hours
Executive$799/moWithin 4 hours
C-Suite$2,499/moWithin 1 hour (priority)

Response times are during business hours (Mon–Fri, 8am–8pm ET). Off-hours tickets are handled first thing the next business day. C-Suite priority support includes weekend coverage for critical issues.

What to Include for Faster Resolution ​

  • What you expected vs. what happened.
  • Steps to reproduce — what you did right before the issue.
  • The conversation or message where the problem occurred (ticket number or timestamp).
  • Whether it's affecting customers right now — we prioritize live customer-facing issues.

Data Access ​

If your issue requires our support team to look at your data, they'll ask for your explicit permission first. Every access is logged in your portal's access log — you can see who looked, when, and why. See Data Ownership.

Built for owners who refuse to sit in every meeting.