Contact — Pazi Documentation

Contact

For help with Pazi, email support@pazi.ai or use one of the contact forms below.

Account support

When you are signed in, open Account → Contact. The authenticated form helps the team associate the request with your account.

Include the affected business, agent, conversation or task, approximate time, and what you expected to happen. Do not include passwords, API keys, tokens, recovery codes, or private customer data that is not needed to diagnose the issue.

Public contact

Use the public contact form for general questions, partnerships, business inquiries, or help when you cannot reach the dashboard.

Report a product problem

Provide a concise reproduction:

  1. The page or channel where the problem occurred.

  2. The steps that led to it.

  3. What you expected.

  4. What happened instead.

  5. The relevant agent, conversation, opportunity, or scheduled-task name.

  6. Browser, operating system, and whether the issue also occurs after refresh.

  7. A screenshot or non-sensitive error message when useful.

For Slack, include the workspace and channel but do not paste bot tokens. For email, include sender, recipient agent address, subject, and approximate time but remove secret or sensitive message content unless it is essential.

Billing help

For plan, funding, charge, cancellation, or payment-method questions, include the account email and date of the transaction. The team never needs your full card number or bank credentials.

You can review the current plan under Account → Subscription and open Stripe's billing portal from Billing Information.

Security reports

Report suspected vulnerabilities privately through support@pazi.ai or the contact form. Include the affected surface, impact, and safe reproduction details.

Do not include live secrets, access another user's data, perform destructive testing, or post exploit details in Discord, Slack, or another public channel.

Feature requests

Describe the problem, who encounters it, how you handle it today, and what a successful outcome would look like. Concrete workflows are more useful than a requested button without context.

Before requesting a new feature, check the relevant guide and ask the operating officer whether the workflow can already be handled with a skill, scheduled task, Slack, email, or a specialist agent.