Contact AveolaWeb — We Actually Answer

Before you write, one honest tip: the fastest answer is often already on the site. Safety questions live in the safety guide, and the mechanics of matching are covered in how AveolaWeb works. If neither covers it, we're listening.

Email us

Email us at support[at]aveolaweb.com — swap the [at] for an @ before you hit send. We write it this way to keep scrapers from harvesting the address, not to make your life harder.

That's the one inbox for everything: questions, feedback, bug reports, and anything about your experience on AveolaWeb. When you contact AveolaWeb, a person — not a script — decides what happens next.

Coins question? Billing is handled the same way: write from the address you use on the site, describe the charge you're asking about, and we'll trace it. No chatbot maze, no ticket number that vanishes into a queue — one inbox, real replies.

Reporting a user

If a call went wrong, the in-call report button is the quickest route — it attaches the context we need automatically. The safety guide shows where it sits, and the community guidelines spell out exactly what counts as crossing the line.

Email works too when the moment has passed: the call already ended, or the problem happened outside a call entirely. Either way, the report reaches the same review process — choose whichever path gets you there fastest.

What to include

The more precisely you can describe the moment, the faster we can find it. A good message usually covers:

What happened, in your own words — a short honest account beats a long polished one.
Roughly when it happened, including your time zone.
If it involves another user, anything that helps us find the call — a nickname, a detail, a screenshot if you have one.

One thing never to include: passwords or verification codes. We will never ask for them, and neither should anyone claiming to be us.

How fast we reply

We answer every message ourselves, as quickly as the queue allows — but we don't promise a fixed turnaround. Some questions take real digging, and we'd rather answer well than answer fast. If your message is about an urgent safety issue, say so in the subject line and it jumps the queue.

You won't get a form letter back. Replies come from the people who actually run AveolaWeb, so when you tell us something is broken or confusing, it lands with the ones who can fix it.

Contact FAQ

How fast will I get a reply?

We read everything ourselves and reply as fast as the queue allows, but we don’t promise a fixed turnaround. A careful answer beats a fast canned one.

Should I report a user in-app or by email?

Use the in-call report button whenever you can — it arrives with the context we need already attached. Email works when the call has ended or the problem happened outside a call.

What should I include when reporting someone?

What happened, roughly when, and anything that helps us find the call — a nickname, a screenshot if you have one. Never include passwords or verification codes, for us or anyone else.

Can I suggest a feature or idea?

Please do. We can’t promise every idea ships, but every single one gets read by a human.

Talk soon

Whether it's a problem or just an idea, the inbox is open. And if everything's working — well, there's a match waiting.

Start Video Chat See How It Works

Talk to a Human at AveolaWeb