AI to run your
Business World

Ecommerce support · RF Supplements

RF Supplements support bot

It sits on the RF Supplements operations CRM and reads the same WooCommerce records the screens do: orders, products and stock, shipping, contacts and inquiries, affiliates and the athlete program. It covers two separate ecommerce sites, the public retail shop and a private business-to-business ordering portal, and keeps them apart, because a trade order and a retail order are not the same question.

Ask it in plain language. Sales for any period against the period before it, what is low or out of stock, where an order has reached, which affiliate a referral came through. It also writes: update a stock count, create a product, or set up a subscription so a repeat order is placed on a schedule.

Answers are the store’s own figures and records, the same ones the operations dashboard shows, because it is reading the same shop rather than a copy kept beside it. When a product name is ambiguous it says so and offers the one it thinks was meant, instead of picking one and being confidently wrong.

Nothing is written until a person says yes. Asked to change stock on a product it cannot find, it reports that, proposes the closest match, and asks which size and what quantity before it touches the record. Reading is free; every write is a proposal with a confirmation step in front of it.

Runs inside the operations CRM, over both of the store’s ecommerce sites.

Member services · Baig Medical Group

BMG Monitor

It watches the Baig Medical Group website and the membership CRM built over it, and answers from the records those hold: members and their contact details, the plan somebody is on and what it still covers, the calendar, and the services already logged against a membership. Membership records only, no clinical detail is held in it, reported by it, or asked of it.

Ask who a member is and what their plan still entitles them to this period. Book an appointment, move one, cancel one. Log a service delivered against a membership, so the entitlement count stays right without anybody reconciling it later. Create a record for somebody who is not in the system yet.

It runs on the CRM site itself as well as in Telegram, so a lookup happens in the same window as the record rather than on a phone beside it. Either way the reply is the member’s own record and what is left on their plan, in a sentence rather than a screen to go and read.

It confirms before it touches anything. A booking, a move, a cancellation or a logged service comes back as a proposal and is written only once a person approves it. It is operator-only: the practice’s own staff use it, members never talk to it, and nothing it reports reaches past the membership.

Built and deployed for Baig Medical Group. It runs on the CRM site and on Telegram, operator only, and records what was delivered against a membership, never a clinical detail.

Operations assistant · DiegoTech

DiegoTech Ops assistant

A conversational front end for DiegoTech Operations, reachable inside the application and from Telegram. It reads the live operations database, tickets, customers, projects, quotes and invoice history, and the time, mileage and expense entries behind them, which is the same data the dashboard, the dispatch board and the billing screen show.

Ask what is open, who a customer is, what a quote covered, what has not been billed yet. Then ask it to do the work: log time, mileage or an expense against a ticket, correct an entry that has not been invoiced, create a lead, customer, quote or project, or turn an accepted quote into a project.

Figures come out of the database at the moment of asking, not from a store of answers kept alongside it, so a number it quotes is the number the application shows. Anything it intends to write comes back first as a card naming the record and its fields, in the same application the change will land in.

Every statement runs as the signed-in user, so the application’s own permissions, not the assistant’s judgement, decide what it may see or change. It cannot be talked into more access than the person already has. And it writes nothing at all until they confirm the record it has proposed.

Built and deployed for DiegoTech, inside app.diegotech.com and on Telegram. Every statement runs as the signed-in user, so the application’s own permissions decide what it may see or change.

1. Alert received

   A fault from the monitoring platform on a customer’s system arrives and is translated into one standard fault code, whichever manufacturer reported it.

2. Zone matched

   The site’s zip code decides its service zone and the primary technician for it.

3. Candidates ranked

   If the primary is not available, technicians in range are ranked by travel time and the work already on their day.

4. Assigned and notified

   The job is scheduled and the technician is told by text and app notification, with a window to accept before it moves to the next person.

5. On site

   Arriving inside the site’s geofence starts the labour clock, so the time on the invoice is recorded rather than typed.

Nobody approves each dispatch. This is the one automation on this site that runs without a person confirming every job: what it may do was set when it was configured, and every step lands on the record the office sees.

Built for Auto Solar Service. Precision Electric is the initial tenant.