Back to Help Center
Troubleshooting

Ask AI support or report a bug

Get better help by sending the right context: what you tried, where it happened, what you expected, and what happened instead.

5 min readUpdated Jun 21, 2026
Ask supportAsk support
Audience

Curators, attendees, and team members who need help with a HereNow workflow.

User need

I need help or want to report a bug in HereNow.

Support works best with reproducible context

A message like "it does not work" is hard to diagnose. A better support request explains the workflow, the page, the action, the expected result, and the actual result.

If the issue affects a live event, mention the event date and urgency. That helps support separate event-day blockers from general product questions.

Report a product issue

1

Open support

Use the support entry point from the site or product interface. If you are signed in, stay signed in so support can understand account context.

2

Name the workflow

Say whether the issue is about event creation, publishing, registration, attendee export, payments, templates, profile setup, or another workflow.

3

Include location

Include the page route, event slug, or public event link when safe. Do not paste private tokens or secret URLs.

4

Explain expected vs actual result

Write what you expected to happen, what actually happened, and whether the issue repeats after refresh or in another browser.

5

Mention impact and urgency

If attendees cannot register, payment is blocked, or an event is happening soon, say that clearly in the first message.

What to include

Context
Example
Workflow
I was trying to publish a draft event after editing the registration form.
Page or route
The issue happened on /events/edit?slug=sample-event or on the public event page.
Expected result
I expected the event to publish and show a public registration button.
Actual result
The button stayed disabled, or the page showed an error after I clicked publish.
Impact
Attendees are waiting for the link, or the event starts tomorrow.

Do not include

Passwords or one-time login codes.

Stripe login credentials or bank details.

Full attendee lists unless support explicitly needs a secure path.

Private API keys, tokens, or webhook secrets.

Identity documents or tax documents outside the proper provider flow.

Unredacted payment card details.

Fast support template

I was trying to [workflow] on [page or event]. I expected [result], but [actual result] happened. This affects [event/date/attendees]. I already tried [refresh/browser/account check].

FAQ

Should I contact support before trying again?

If the action is low risk, you can refresh and try once more. For payment, deletion, cancellation, or event-day issues, ask support before repeating the same action many times.

Can I send screenshots to support?

You may send visual evidence when it is safe and redacted. Do not include sensitive payment, bank, identity, or attendee data in ordinary messages.

What if attendees are blocked right before an event?

State the urgency in the first line, include the event link or slug, and describe the attendee impact clearly.

Related guides

Publishing7 min read

Preview and publish your event page

Preview the page like an attendee, resolve blockers, then publish with the right visibility setting.

Read guide
Registration7 min read

Manage registrations and export attendee data

Use the registration dashboard to review attendee status, check in participants, and export the list when needed.

Read guide
Payments6 min read

Connect Stripe payouts

Connect Stripe before relying on paid checkout, and understand what HereNow can and cannot verify for payouts.

Read guide