Something not working, or not sure how something should work? Email us. A person reads every message and replies within one business day — and never later than two.
Both options below are open to everyone — customers, people evaluating Verifa, and workspace admins who just installed our Slack app. Neither requires a Verifa account, and there is nothing else to sign up for.
Write to us directly. No account, no ticket portal, no sign-up. Include as much detail as you can and we'll pick it up from there.
Email SupportThe same inbox, reached through a form if you'd rather not open a mail client. Works from any browser and needs no login.
Reaches the same team, with the same response time.
Open the FormA human replies to every message. These are the targets we hold ourselves to, measured from when your message arrives:
| What you sent | First reply |
|---|---|
| Something is broken in production Verifications failing, alerts not arriving, an integration disconnected | Within one business day, usually much sooner |
| A question about setup or behaviour How a feature works, why a result looks the way it does | Within one business day |
| Anything else Pricing, plans, feature requests, partnerships | Within two business days |
| A security or privacy matter Vulnerability reports, data subject requests | Acknowledged within one business day |
Business days are Monday to Friday. If your message arrives over a weekend or a public holiday, the clock starts on the next business day. We don't route you through a bot, and we don't close a conversation until you tell us it's sorted.
None of this is required — send what you have and we'll ask if we need more. But including these usually turns two round trips into one:
Please don't email us personal data belonging to your end users — no document images, dates of birth, or ID numbers. An internal reference or a session ID lets us find the record without anyone's personal information travelling through email.
Messages stopped arriving. Most often the bot was removed from the channel, or the channel was archived. Open Integrations in your Verifa dashboard — a broken connection shows the reason and the fix right on the card.
Nothing posts to a private channel. Private channels need the bot invited explicitly. In that channel, run /invite @Verifa, then use the Test button on the connection.
Too many or too few messages. Which events post is configurable per connection, as is the channel each one goes to. The setup guide walks through routing and reminder cadence.
Still stuck? Email support@withverifa.com and mention your Slack workspace name — that's enough for us to find the connection.
Plenty of questions have a written answer already:
Support handles almost everything. These exist for the cases where it shouldn't: