no-code AI customer service

The Guru is operable end-to-end from a web dashboard. There is also a full API for teams that want one, but no part of the standard setup requires writing code or filing tickets with a vendor's professional services team.

What the dashboard covers

• Knowledge: crawl your website and upload documents, then re-index when you add or remove content. Add manual Q&A in your own words through the Instructions field and through uploaded documents.
• Channels: enable web widget, email, phone, SMS, WhatsApp; each has a guided connector.
• Brand voice: describe the persona and tone you want in a single free-text field.
• Routing and handoff: when to auto-reply, when to escalate, where to send escalations.
• Integrations: Shopify, CRMs, and order systems wired up as deterministic flows in the Flow Designer.
• Analytics: live conversations, what customers ask, and where your content has gaps.
• Users and permissions: invite teammates with scoped roles.
• Billing: plan changes, invoices.

Configuration here is option-selection, not code authoring.

A typical first hour

Minute 0 to 5: sign up, enter your website URL, the crawler starts.

Minute 5 to 15: while the crawl runs, set up brand voice (persona, tone, two example exchanges) and pick widget colors.

Minute 15 to 30: review crawled pages and upload one or two documents covering anything the crawl missed, then re-index.

Minute 30 to 45: paste the widget snippet onto your site (or have whoever manages the site do it). Test it with three real questions.

Minute 45 to 60: enable email forwarding from support@. Send a test message; verify the reply.

At the end of an hour you typically have web chat and email live with grounded answers in your brand voice.

Why no-code works for this domain

Customer service automation used to require explicit flow building: every question mapped to a node, every branch authored by hand. With RAG, the configuration shifts from "model every possible conversation" to "point the AI at the truth." That removes the largest piece of work that historically required a developer.

The remaining configuration (channels, voice, routing rules, integrations) is mostly option selection rather than code authoring. There are a few credential fields for channels you own under the Bring Your Own Channels (BYOC) model: connecting your own Twilio voice or SMS number means entering your Twilio Account SID and Auth Token, and enabling the self-hosted CSAT survey means pasting your CSAT site URL and token secret. These are paste-in fields in the dashboard, not code you write.

A worked example: enabling Shopify

1. In the dashboard, click Integrations and choose Shopify.
2. Enter your myshopify.com URL.
3. Authorize a custom app with your Shopify admin credentials.
4. The connection shows as active against your live store data.
5. The Guru can now answer order and product questions in real time.

Order-specific details are gated behind one-time-code verification, so account information only reaches the right person. Total elapsed: a few minutes, no engineer involvement.

A worked example: changing brand tone after launch

You realize the replies sound a touch too formal.

1. Dashboard, Brand Voice.
2. Edit the free-text voice field: change "professional" to "professional but friendly" and add an example of the new feel.
3. Save.

The next message sent on any channel uses the updated voice. No retraining, no deploy.

When you do want code

The platform exposes a REST API, webhooks, and an MCP endpoint for teams that want to:

• Push events from their own systems (a new order from a non-Shopify cart, an appointment booked in a custom system).
• Wire a backend integration as a deterministic flow in the Flow Designer.
• Build automations triggered by Guru events (when a conversation is escalated, open a ticket in your own tooling).
• Schedule re-crawls so the knowledge base refreshes automatically, which is available via the API.

The API is optional. Standard usage never touches it.

Trade-offs

• Theming covers eight preset color themes or custom color pickers, a custom launcher icon, chat starters, and teaser bubbles; beyond that, deeper widget customization is out of scope for the no-code panel.
• Edge integrations not yet built need a deterministic flow scoped during onboarding, or you can wire your own systems through the REST API, webhooks, or MCP endpoint.
• Custom JSFE workflows for proprietary CRM, niche commerce platforms, or industry-specific compliance are scoped during onboarding rather than self-serve toggles.

What this changes in practice

Most teams that buy enterprise customer service software end up needing internal engineering or paid professional services to get value from it. Self-serve provisioning means a service business owner, a marketing lead, or an ops manager can run the entire setup themselves over a single afternoon. Faster time to value, lower switching cost, and no dependency on a developer roadmap.