Syfatech

Our work · Case study

Syfa: our own AI assistant, built the way we build for clients.

Syfa answers visitors on syfatech.com from our own content, hands them to our team when it matters, and books real calls. We designed it, built it and now run it.

At a glance

One assistant, design to run.

The need
Visitors were reading a lot and still not understanding what we do. We needed someone to answer questions at any hour, and to turn interest into a booked conversation without a form that goes unanswered.
What we built
An AI assistant that answers only from our approved content, offers a callback when a visitor wants a person, and lets our team confirm the booking from one email, which creates the calendar event and the invitation.
Design
Scope, tone and rules written down first: what Syfa may say, what she must never say, and when she hands over to a human.
Build
Delivered in one sprint: grounded answers, then callback and meeting capture, then guardrails, monitoring and launch.
Run
Live on syfatech.com with daily and monthly limits, masked logs that delete themselves, and her knowledge rebuilt from the site whenever the site changes.
Team
One team developed it, launched it and monitors it. The people who built Syfa are the people who run her, so a fix never waits on a hand-off.
Technology
Cloudflare Workers and key-value storage, Anthropic's Claude Haiku 5.5, Zoho Calendar and Zoho Meeting, plain JavaScript on the page. No framework and no third-party tracking.

What Syfa does

Answer, hand over, book.

  1. 1Visitor asks
  2. 2Syfa answers from our content
  3. 3Visitor requests a callback
  4. 4Our team confirms in one click
  5. 5Event and invitation created
Answer

Grounded answers

Every reply comes from a knowledge file built from our public pages. If the answer is not there, she says so and points to the team. She never invents prices, timelines or client names.

Hand over

Callback on request

When a visitor wants a person, Syfa offers a short form: name, email, time zone and a preferred slot. Our team receives it by email within seconds.

Book

One-click confirmation

The team opens the request, checks the live calendar and confirms. The event, the video link and the invitation are created in one step, and the slot disappears from the picker.

Safe by design

What we put around the model.

An assistant on a public website is only useful if it can be trusted. These are the controls that ship with it.

Grounded only

Answers come from approved content. Questions outside our business are politely steered back, and instructions hidden in a visitor's message are treated as questions, never as commands.

Fails closed

If limits or storage cannot be checked, Syfa rests and the visitor is pointed to the contact form instead of getting an unchecked answer.

Spend limits

A daily conversation cap, an hourly cap per visitor and a monthly spend stop keep the running cost predictable and abuse bounded.

Privacy by design

Email addresses and phone numbers are masked before a chat is stored, and chats delete themselves after 30 days. Callback details are kept for up to 72 hours, longer only if a call is booked.

A human confirms

Syfa proposes; a person decides. Nothing is added to the team calendar until our team confirms, and the link in the email works for one request only.

Calendar safety

Offered slots are held while a request is pending, checked against the live calendar again at confirmation, and released if the request is declined.

How we built it

One sprint, one team.

We started on 26 October 2026 and close the sprint on 6 November 2026, once testing, live checks and the corrections made with direct users are done.

Phase 1

Grounded Q&A

Knowledge base from the site, the chat endpoint, the on-page widget and a 20-question test set run before anything went live.

Phase 2

Callback and meetings

Offering a callback in the conversation, capturing details, delivering them to the team and, later, booking the confirmed call from the email.

Phase 3

Guardrails and launch

Scope limits, abuse protection, the cost cap, the privacy page and a go-live decision by the owner, with a one-switch rollback.

What we learned

Notes for the next one.

Content is the product
The assistant is only as good as the page content behind it. We rebuild her knowledge from the site on every change, so what she says and what the site says cannot drift apart.
Decide the limits first
Writing down what she may not do, and what a failure looks like, was quicker than fixing it after launch.
A widget must own its look
When we moved the site to a new light theme, her text briefly inherited the page colours and became hard to read. She now carries her own palette, so a site redesign cannot break her.
Real users finish the job
Testing and live checks with direct users surfaced reconfigurations and corrections we would not have found alone. We treat them as part of the build, not as an afterthought.
Test on a real phone
Most visitors meet her on mobile, where the keyboard, the screen and the thumb change everything. We test her there, not only on a desktop.
This is version one
More versions will follow as we find room to improve and as new business problems come up. Syfa is built to grow with them.

For your organization

Want an assistant like Syfa?

Our aim is for Syfa to be the answer when you have visitors to your site: answering them at any hour and getting them to a conversation with your people. The same approach works for support, sales, internal help desks and onboarding, grounded in your content and limited by your rules. Tell us what you would want it to do.

Book a call Ask Syfa

Get started

Three ways to reach us.