Escalations
When a client asks for a new page, a layout change or anything that needs code, the editor does not fail and does not guess. It holds the request and lets the client send it to you.
No credit card, cancel anytime.
Benefits
A refusal arrives with a way forward: send it to the team. There is no dead end and no support address to hunt for.
The request reaches you with the client's original message, not a sanitised error code.
Nothing reaches you until they choose to send it, so your queue does not fill with half-formed thoughts.
Escalations are delivered by email and Slack, configured per workspace.
How it works
A new page, a new section, a layout change or an integration.
It explains that this one needs the team, and offers to send it on.
They choose to send it to the team. Only then is a ticket created.
With their message attached, ready to approve, publish or turn into a pull request.
Use cases
New pages are out of scope by design. The ask reaches you as a brief instead of as a surprise.
Example
“Can we add a careers page?” becomes a ticket carrying the client's own wording, rather than a broken edit you have to reconstruct.
A new component, a form or a third-party embed routes to you as work, not as a failure.
The client cannot edit it, but they can still ask, and you still hear about it.
Every escalation is stored against the site, so what was asked survives the conversation.
Pricing
Everything included. $39 a month for 5 sites, then $10 each.
50% off for 12 months
with code BREW50 for the first 20 customers (11 left)
Billed monthly.
Billed $312 yearly. Save 33%.
FAQ
Give your client the keys to the content. Keep the keys to the code.
Prefer to talk first? Book a 30-minute call