Refunds

Last updated:

|Edit this page

Most of the requests we receive fall under the following scenarios:

  • Learning curve: just got off of the startup plan/new client accidentally used us a lot
  • Unexpected stardom: side project sudden volume spike
  • Under attack: bot spike/abusive user drove traffic which in turn increased posthog usage

Eligibility Criteria

Customer must meet the following criteria to get a refund:

  • The request is made within 30 days of the billing date.
  • The customer provides a reasonable explanation for the request, fitting into one of the above scenarios.
  • The account does not show signs of fraudulent activity or abuse of PostHog services.

Scenarios and Procedures

Learning Curve

We issue refunds in this category if this is the first bill >$1 and/or they meet criteria as explained above.

Next steps

Unexpected Stardom

We issue refunds in this category if this is the first bill >$1 and/or usage spiked by >200% compared to their average usage over the past 3 months, and/or the account is a non-commercial or a hobby project.

Next steps

  • Use Refund - Unexpected Stardom email template to respond to the customer if they match criteria.
  • Assign the refund request to the RevOps team in Salesforce for processing.

Under Attack

We flag accounts with unusual activity spikes for review, and refund the overage amount once the issue has been resolved. The refund will cover any amount exceeding the average usage of the three months preceding the spike.

Next steps

  • Use Refund - Under Attack email template to respond to the customer if they match criteria.
  • Assign the refund request to the RevOps team (Mine) in Salesforce for processing.

Repeat incidents

For first incident response, we follow standard policy above and provide guidance for preventing future incidents (e.g. ask them to implement billing limits).

Subsequent Incidents:

  • Check if the user followed PostHog’s recommendations in the previous incident.
  • We issue up to 50% refund or up to 100% credits that can apply on future usage depending on the issue severity and previous actions taken to prevent spikes.
  • Provide warning that in the event that this happens again PostHog may not be able to support. Remind them of the measures necessary to take to avoid such issues going forward.
  • After 2 incidents, further refunds for similar issues may be declined unless there are extraordinary circumstances.

Next steps

  • Use Refund - Repeat Incident or Refund - Same Issue email templates to respond to the customer if they match criteria.
  • Assign refund request to RevOps (Mine) in Salesforce for processing.
  • Escalate any cases that do not match criteria above to RevOps for review.

Questions?

Was this page useful?

Next article

Automations

Automations As Vitally connects all of our Product, Stripe, Zendesk and HubSpot data together it's the best place to trigger automations via Playbooks. These Playbooks can call a webhook after Accounts or Users meet certain criteria. This allows us to call out to Zapier to use their inbuilt actions to update Zendesk, HubSpot, Slack and more. We use Zapier extensively throughout the company for automation. There is a shared Zapier login in 1Password. Connecting everything together…

Read next article