BrandPilot
A structured campaign brief triggers several kinds of output through one interface, with orchestration in the background and less manual back-and-forth between tools.
TKM-03AI SYSTEMSLIVE
HelpBot Ticket Desk
Support operations · Webhook
Web and email requests enter one process, are classified by AI and end up as a clear ticket with routing logic and a signal to the team when a human decision is needed.
01 / Problem
Requests arrive through contact forms, inboxes and internal channels. Without structure, someone has to read each message, judge urgency, send it to the right person and remember what has been handled.
02 / What was built
The system combines web form and email intake into one normalised JSON shape. The AI layer returns category, priority, assigned team, summary and a confidence level. The ticket is stored in MySQL, and Slack receives a notification with enough context for the team to act quickly.
03 / How it works
- Webhook and IMAP intake land in the same data structure.
- AI returns strict JSON for category, priority, team assignment and confidence.
- A MySQL record creates a stable ticket and a basis for history.
- Slack routing sends the context to the team, while edge cases stay on human review.
04 / Security notes
- Strict JSON output means free text from the model is never executed or passed on blindly.
- Low-confidence cases go to a person instead of being routed automatically.
- Incoming messages are untrusted input and are a natural target for prompt injection, which makes this system a candidate for adversarial testing.
05 / Operational value
The key value is not the idea that AI decides everything. It is that uncertain cases go to review before the system makes the wrong routing decision.
SCREENSHOTS
