Support

Before you write

Many answers are already in the docs:

• Troubleshooting: refused calls, and calls or meetings that didn’t go as planned;
• Connect your agent: the steps for ChatGPT, Claude and other agents;
• Pricing and billing: what calls cost and how credit works;
• the questions people ask.

What to put in your message

Write from the email address you sign in with, so we can find your account. Then tell us:

• what you asked for, and what happened instead;
• the call’s ID, from the dashboard or your agent (it starts with call-);
• any error message or refusal code, word for word;
• when it happened, with your time zone;
• the agent you use, such as ChatGPT, Claude, Claude Code, Cursor or the REST API.

Never send us your API key, a sign-in link or a card number. We will never ask for them.

Your account and charges

• A charge looks wrong. Tell us within 60 days of the charge.
• Someone else may be using your account. Revoke your API keys and connected apps in the dashboard, then write to us straight away.
• You want to close your account. Write from the address you sign in with.

Our terms have the details.

If Smitline called you

Smitline calls people and joins meetings for its users. It says whom it is calling for, and that it is an AI assistant. For questions about the call itself, ask the person it called for.

• To stop calls to your number from every Smitline user, or to ask what we hold about you, write to [email protected] with your number.
• To report a call that seemed wrong, such as a scam or harassment, write to [email protected] with your number and when the call came.

Our privacy notice says what we keep and for how long.

Report a security problem

If you find a security problem in smitline.com or Smitline Cloud, write to [email protected] with “Security” in the subject. Tell us what you found, how to reproduce it, and what someone could do with it.

We confirm that we have your report within 2 business days, and we tell you when the problem is fixed.

Please don’t look at or change other people’s data, call or join meetings with people who haven’t agreed, or slow down the service. Give us time to fix a problem before you tell anyone else. If you want to test something, ask us first: our terms allow security testing only with our written permission.

For the open-source engine, report privately on GitHub: open the engine’s Security tab (opens in a new tab) and choose Report a vulnerability.

The same contact is in our security.txt file.