Contact the team

Tell us what you are trying to solve and we will reply with the clearest next step

Use one contact path for product questions, billing follow-ups, partnerships, or workflow requests.

A little context upfront helps us answer faster and with less back-and-forth. This page is designed to help you send that context in one pass.

One page for product, billing, and partnership conversationsReplies aimed at the next useful action, not a generic acknowledgementWorks for quick questions and more detailed workflow requests
Response approach

Built to reduce back-and-forth

The strongest contact messages make the situation clear early. We use that context to route your request well and respond with something more useful than a placeholder reply.

1

Pick the subject that best matches your situation so the message reaches the right context faster.

2

Use the message field to explain the exact blocker, billing question, workflow, or timeline you are dealing with.

3

Expect a reply that helps you move forward instead of one that only confirms we received the note.

Primary contact form

Send the context once

Share the goal, blocker, or billing detail behind your request and we will answer with the most useful next step we can.

Product and onboarding questionsBilling and subscription supportPartnership or workflow scoping
Why this works

A clearer first message usually leads to a better first reply

Use the subject for routing and the message box for specifics. That gives us a better chance of answering well on the first pass.

1

Name the situation clearly so we can route the request faster.

2

Add the detail that matters most: billing step, workflow, campaign context, or partnership goal.

3

Tell us what kind of answer would unblock you most so we can keep the reply practical.

For billing questions, mention the plan name or the last checkout step you saw.
For workflow or partnership requests, add timing, goals, and the use case you want help with.
When to use each route

Prefer a direct route or a faster handoff?

Choose the option that best matches how much context your request needs.

Short product or billing questions can often be handled in the first reply when the situation is clear.
Partnership and workflow requests go more smoothly when you include scope, timing, and goals.
If the details matter, the form is still the best way to keep the full context together.

General support

Best for straightforward product questions, billing clarifications, or any request that needs a direct reply.

support@cpmcalculator.dev

Email support

Partnerships and custom requests

Use the form when you need to explain integrations, campaign support, heavier usage, or project-specific goals.

Best when scoping details matter

Open the form

Response expectations

We aim to respond with a useful next step, not just confirmation that your message was received.

Usually within 1-2 business days

Read common questions
Before you send

Questions we can usually answer fastest

If one of these sounds like your situation, mention it in your message so we can reply with the right context sooner.

Can I ask about billing or plan changes here?

Yes. Include the plan you are on, what you expected to happen, and any recent checkout or renewal details if you have them.

What should I include for a partnership or workflow request?

Share the use case, expected volume, timing, and what kind of support or collaboration you are looking for.

How quickly do you usually reply?

Most messages receive a response within 1 to 2 business days, with more detail when the request includes enough context.

Can I send feedback even if I am not on a paid plan?

Absolutely. Product feedback, questions from new users, and improvement ideas are all welcome.