Behind the build
How our intake works: four ways in, one record
The website form, info@, Bookings and a Microsoft Form all land on one Dataverse record, acknowledged in seconds. What's live and what's still in build.
The first thing anyone sees of TNT is what happens after they ask us something. A company that sells “one accountable partner” can’t lose an email in a shared inbox. So intake was the first function I built, and it’s the one you can test yourself. Everything I describe as live below was tested on October 16, 2026.
Four ways in
You can reach us four ways: the form on this site, an email to info@tnttech.io, a booking on the 30-minute call calendar, or the Microsoft Form we used before this site had its own forms, which we’re retiring. Each one is a Power Automate flow, and all four write to the same table in Dataverse.
That table is the one record. If you fill in the form and then book a call, you’re one lead with both on it, not two leads in two systems. Every agent we build reads from that record and writes back to it, so nothing depends on someone copying details from one place to another.
An answer in seconds, a reply from a person
The acknowledgement is automatic. In our test runs it went out about two seconds after a website form and about one second after a Microsoft Form response. We promise it within minutes, because a promise should hold on a bad day too.
The acknowledgement isn’t the reply. A person reads every request and replies within one business day. Each new request also posts to our Teams channel with what you told us, so the reply doesn’t depend on someone watching an inbox.
The Teams card
Everything an agent drafts goes to an approval queue in Teams before it goes anywhere else. It’s a card with two buttons, Approve and Reject, and the decision is written back to the record. Nothing leaves until a person taps one. We proved that round trip in production on October 16.
Today the queue is live and the agents that will fill it are not. The Scorecard agent is in build. The content agent and the call-prep agent are planned. When they come online, they start where every TNT agent starts: drafting only, with a person approving each draft. An agent earns the right to act on its own after a measured run of approved work, and one reversed action drops it back a level.
What broke on the way
Two things, both small.
First, email. Our info@ address is an alias, and Exchange resolves an alias to the mailbox’s main address before a flow sees the message. The first version of the flow filtered on “sent to info@”, so it never fired. We dropped the filter and skip our own domain instead.
Second, Bookings. The flow was watching an old booking page, not the calendar the button on this site uses, so a call booked from the site never reached the record. We pointed the flow at the right calendar and booked a test call to prove it.
Neither would show up in a demo. Both would have cost us a lead.
What’s next
The control plane is in build: one view of what each agent did, what’s waiting and what it cost, with one switch that stops them all. So is the Scorecard agent, which will draft each free Scorecard from the request this intake creates, for a person to approve.
None of this is exotic. It’s Microsoft 365, Power Automate and Dataverse, the stack a growing company already pays for or can add. Booking and intake is also one of our quick-win workflows. And if you’ve used the form on this site, you’ve already seen it work.
The full list of what runs TNT, with what’s live, in build and planned, is on How TNT runs.