After-hours outcome fees explained (booked + dispatched)

Definition

After-hours pricing gets confusing fast when every provider uses a different unit. Pink Callers keeps it simpler on purpose. The desk itself is a flat $299 per week for nights and weekends, then outcome fees are layered on when the coverage actually produces a result: $25 when the Rockstar books the job and $35 when the situation becomes a dispatched job.

That structure matters because it separates coverage from conversion. You are not paying daytime desk pricing for quiet overnight hours, and you are not trying to reverse-engineer a per-minute bill that says a lot about call length and very little about value. The pricing is tied to the way contractors think: what did the desk protect, book, or move forward?

Transparent booked and dispatched fees exist so owners can model night economics without mystery minutes. Compare that clarity to any per-minute night bill before you renew coverage.

When to use

This model works well for owners who want predictable baseline coverage without pretending every night generates the same demand. Some weeks are quiet. Some weeks are stormy, hot, freezing, or packed with emotional emergency calls. A flat base plus outcome fees reflects that reality better than a night plan that quietly runs the meter while the caller sits on hold.

It is also useful for operators who want clean internal conversations about payback. When the pricing units are clear, the owner, dispatcher, and office manager can all evaluate the same model. That makes it easier to decide whether the night desk belongs in the budget, whether emergency marketing should keep running, and what booking standards the coverage has to hit.

Failure modes

The most common mistake is looking only at the $299 line and ignoring what the outcomes represent. If you model the base without the booked and dispatched fees, you are understating cost. If you model the fees without the revenue or relationship value they protect, you are understating return. Operators need the full picture.

Another failure is poor definition. If your team has not agreed on what counts as booked, what counts as dispatched, and how those states are reflected in the CRM, then even transparent pricing becomes confusing. The desk and the office have to use the same language, or the invoice review turns into a debate about semantics instead of performance.

• Comparing only the $299 line and ignoring outcomes
• No definition of what “booked” means in your CRM
• Mixing daytime overflow into after-hours math

Proof

Pink Callers adds one more transparent layer where needed: pAIge overflow and certain admin or clarification tasks are metered at $1.99 per minute. Michelle keeps that visible because AI should be a pressure-relief valve, not a black-box charge. Again, the goal is operator clarity, not mystery savings.

The proof here is not a vague "custom quote." It is that owners can plug their own volume into the estimator, compare base plus outcomes to actual ticket economics, and decide whether the model fits. That kind of disciplined pricing is one reason the desk works well for tech-adopting trades businesses that want systems, not surprises.

Action

Use `/plans#calc-afterhours` with your real weekly night volume, then review the result next to your average booked and dispatched outcomes. If your team serves urgent trades, it helps to keep a trade lens open too, especially `/trades/plumbing` or `/trades/hvac`, while you do the math.

After you run it, take the questions to `/contact` with your definitions of booked, dispatched, and overflow. That conversation should settle whether you need pure coverage, tighter process, or a hybrid setup where pAIge handles the spikes and Rockstars handle the moments that protect the brand.