Before the order
Size, hours and what is in stock, from your list.

We have not shipped a named ecommerce chatbot on this site. We have shipped chat and voice that answer from a source you approve, and retail work such as Dubai Fashion Week. This page is that work, scoped to a shop.

Hours, stock notes and policies you approve, not a guess.
A person still owns the cart, the refund and the complaint.
The CRM or inbox keeps what was asked and what was said.
A process review is the usual first step. You can also look at related work or bring a specific workflow.
The same agent pattern we use for CRM and inbox work.
Call24 and the hotel voice receptionist are the live examples.
The bot does not invent a price or a delivery promise.
Dubai Fashion Week is guest and event work, not a shop bot. It is the retail case we can show.
Size, hours and what is in stock, from your list.

A status from the system of record, or a handoff.

The bot collects the facts. A person decides.

Guest questions, as on the hotel voice receptionist.

The stack behind the systems on this site.
We sit with how your team works today and pick the workflow that is worth building first.
You get the shape of the product, the systems it touches, and a scope you can agree.
We build, test with your people, and keep a human in the loop where the agent decides.
We launch with you and stay for support after the system is in use.
Since 2011
in business
1,000+
apps delivered
99%
client satisfaction
10+
billion-dollar companies served
Brown Tech has been in business since 2011. We design and build custom software, AI agents and automation for teams that want software built around how they already work.
We start with the system your team needs, connect it to the tools you already use, and add AI where it removes real work.
Not as a named case on this site. We have shipped chat and voice agents, and retail event work. This page uses those, scoped to a shop.
No. Payment and refunds stay with the person and the tools you already use.
Timing is agreed in the process review, project by project. That review comes before build starts.
Cost is scoped per project after the process review.
Support after launch is part of how we work. The shape of that support is written into the scope.
Only if that write is in the scope, and only with the review step you mark.