Receipts, method & support
Inspect what we can prove today.
Here is the method, step by step, and everything it has produced so far: a documented test on our own phone line, and one install underway. We do not have client results yet, and we are not going to imply otherwise.
This is our own phone line, tested on ourselves first — not a client's result, and not a promise about yours.
Receipt method
Define the test
Record the path, time window, and expected handoff before running it.
Exercise the path
Run the customer-like scenario and capture the observed events.
Record exceptions
Show failures, missing events, and ambiguous behavior beside what worked.
Rank the next step
Recommend only what the receipt supports and label estimates as estimates.
Published support expectations
- Hours
- Monday–Friday, 9am–5pm Eastern
- Standard response
- Standard requests: we respond within one business day
- Critical interruption
- If a critical service interruption happens, we acknowledge it within four business hours
- Boundary
- No guaranteed weekend response
Run the same check on your own line.
That is the method, not a result. If you want it pointed at your business, book fifteen minutes and we will walk the same path.