INSIDE OUR OWN WORKFLOW
A new inquiry.
Ready for your review.
An inquiry should reach the person who can act on it without being copied twice or losing the reply they are preparing. Here is a recorded demonstration of the inquiry-handling software used in TundraTexture’s private office.
Recorded September 13, 2026. Real software, fictional business details, isolated local demonstration. This is not a customer case study.
The request
Alex at Example Maintenance
“We run a small maintenance crew in Mat-Su. Estimates are recorded in a spreadsheet, but follow-ups get missed while we are on jobs. Can you help us find a better process?”
Selected goal: Follow up on estimates.
The demonstration starts with an inquiry record in the format our website receives. It runs the same inquiry-import code as our deployed office. It does not submit this fictional request to the live website.
What happened when we ran it
One inquiry reached the review queue.
The software created one item with the supplied business details and marked it for owner review. It kept the stated goal and message together. The original submission was unchanged.
The reply stayed with a person.
The inquiry import did not generate a reply or contact the customer. We entered the example reply below as an owner-written draft and marked the item reviewed.
A repeat check created no duplicate.
We ran the import again from the beginning. The queue still contained one item. The owner-written draft and review state were preserved.
The owner-written draft
“Thanks, Alex. Who checks your open estimates, and how do you record customer replies today? We can start by reviewing that process before discussing a pilot.”
Result: saved for review; not sent. This text was written for the demonstration, not generated by AI.
The recorded results
- First check: one new inquiry marked for review.
- Repeat check: zero new items; one inquiry remained.
- Owner’s work: draft and review state retained.
- Original request: unchanged.
- External actions: no emails sent and no AI calls.
These results were checked against the saved records from the run. They demonstrate the handling of this sample inquiry, not every possible failure or business situation.
Where Tessa fits
The Tessa guide on our public website answers from approved company information and helps visitors prepare an inquiry for review. Our separate private office brings website inquiries to the owner’s queue. Its email-review features can prepare drafts from connected business mail; that separate email and notification path is not exercised in this demonstration.
This inquiry step uses fixed rules because it does not need AI to preserve a visitor’s details and avoid duplicates. Important decisions, pricing and customer replies remain with the owner. The public guide cannot access the private inbox.
What this means for your business
For a trades business, a useful starting point may be making sure inquiries reach the office with enough information and a clear person responsible. Following up on an estimate is a further workflow: it needs a reliable estimate status, customer preferences, agreed timing and a way to stop when the situation changes.
We assess those requirements against your existing tools before proposing a pilot. This example does not establish that your software is connected, that a telephone receptionist is available, or that more revenue is guaranteed.