Short answer: When your account and qutee line are already provisioned, you can usually configure the agent, FAQs, and capture fields and complete the first test call in about 30 minutes. Whether callers reach you after that depends on call forwarding and any integrations you still need. Number porting, SIP projects, and complex CRM work sit outside this window. The broader flow is covered under How it works.
| Milestone | Typical duration | What you have |
|---|---|---|
| Configured | ~20 min | Agent active, FAQs and capture fields in place |
| Test-ready | ~30 min | First test call reviewed in Calls |
| Customer-live | depends on telephony | Company number forwarded, real callers reach qutee |
What counts toward 30 minutes, and what does not?
Count login, agent setup under Agents, FAQs and information capture, optionally one calendar or forwarding rule, plus a test call in Calls. Exclude account invites, telephony provisioning, porting, and custom system integrations.
| Inside ~30 minutes (your setup) | Before / alongside (often with support) |
|---|---|
| Login (MFA if required) | Invite / account activation |
| Agent greeting, role, task, voice | Number / SIP provisioning |
| FAQs and capture fields | Zammad, TANSS, CRM Catch, and similar |
| Optional: Google/Microsoft calendar or forwarding | Number porting |
| Review a test call | Custom workflows |
You keep your existing number. Typical go-live is a simple call forward to the line qutee provides. Callers never need a new dial string.
Minutes 0-5: Sign in at app.qutee.ai
Open app.qutee.ai, sign in, and complete MFA if your policy requires it. You will then see Agents, Calls, Telephony, and Integrations.
After sign-in you land in the overview. MFA (for example TOTP or email) is policy-driven. Budget one to two minutes.
Without an enabled account, the clock does not start. In practice, new customers often receive an invite. No access yet? Reach out via Contact.
Minutes 5-12: Configure the phone assistant under Agents
In Agents, set organization and assistant details: name, persona, role, task, instructions, greeting, voice, and timezone. Mark the agent active when it is ready to test.
Steer the assistant with clear fields:
- Organization: business name and short description
- Agent: display name, persona, role, task, instructions, greeting
- Voice: active voice, with optional preview
- Timezone: so schedules and greetings stay accurate
- Active: turn on only when the script feels right
Personality, Intent, Availability, and Quality can wait. For the first half hour, a crisp base agent is enough. More: AI phone assistant.
Minutes 12-20: Add FAQs and information capture
Add answers to common questions (Answer questions, Inquiry) and required fields for complete requests (Capture information, Capture). Optionally wire notification emails for new items.
Two building blocks that set qutee apart from rigid menu trees:
- Answer questions: reusable answers for hours, directions, parking, and similar.
- Capture information: named fields (name, plate, issue description) stored on the call record.
Bring a short prep list: five FAQ answers and three to five required fields. Details: Answer questions & capture information.
Minutes 20-26: Calendar, forwarding, or business hours
Add one or two extras: calendar for booking, forwarding destinations, or business-hours behavior outside your windows. Stacking more in the same sprint usually blows the timebox.
Appointment booking (Google Calendar or Microsoft 365)
In Integrations, connect Google Calendar or Microsoft 365/Outlook and configure booking (duration, buffers, booking horizon, calendars). Appointments land during the call instead of after a callback chain. See Appointment booking and Integrations.
Call forwarding
Define destinations and weekly windows: sales by day, on-call at night. qutee can qualify first and transfer only when a human is needed. More: Call routing.
Business hours
Enable the availability schedule and pick outside-hours behavior: announcement or forward. First-line, overflow, and fallback remain under your control. Overview: Business hours and availability.
Ticketing (Zammad, TANSS) and CRM Catch belong in production, not usually in the same 30-minute first pass.
Minutes 26-30: Test call and review in Calls
Call the qutee test line, walk through greeting, FAQ, and capture, then open Calls to inspect the summary, fields, and status.
Check that:
- the greeting and organization sound right
- FAQ answers match what you wrote
- capture fields come back complete
- forwarding or booking fires when expected
Calls shows AI summaries, structured data, tags, and open/done status, often without replaying the full recording. Tweaks here beat a full rebuild.
After the 30-minute setup: call forwarding and go-live
Forward your company number to the qutee line and place a real inbound call. That is when customers reach you, often within about an hour end-to-end when telephony is already provisioned.
Common patterns:
- First line: qutee answers immediately
- Overflow: qutee covers parallel calls
- Fallback: qutee steps in after a ring timeout
If forwarding is not ready, you are test-ready, not customer-live. Porting or complex SIP work is out of scope for the 30-minute narrative. See also ready to go live in about an hour.
Can every AI phone assistant be set up in 30 minutes?
No. The 30-minute claim applies to a straightforward qutee setup with a prepared account and provisioned line: configure the agent, add FAQs and capture, optionally set routing or a calendar, then test.
Other assistants often need training data, new numbers, a new phone system, or multi-week integrations. With qutee, the clock also stretches once porting, SIP, CRM, or ticketing enter the picture. The half hour is the configurable core, not every project.
Example: trades business (heating, after-hours)
A heating contractor wants after-hours callers answered without dumping them into a queue. Prep might look like this:
FAQs (Answer questions)
- Opening hours: Mon-Fri 7:30-17:00, Sat by appointment
- Emergency service: available outside hours, surcharge may apply
- Service area: city and surrounding area (about 40 km)
- Parking: keep the yard entrance clear, ring "Workshop"
Capture information
- Name and callback number (required)
- Address or site
- Appliance type (gas, oil, heat pump)
- Short problem description
- Urgency (water leak / heating down / advice only)
Forwarding
- Daytime (7:30-17:00): office extension
- Evenings and weekends: on-call technician mobile
- If busy: take a message, email team@…In the app you enter this under Agents (FAQs and capture) and configure the forwarding windows. The test call confirms greeting, answers, and fields before you forward the company number.
What can extend setup time?
These items sit outside the 30-minute clock on purpose:
- Number porting: moving a number to a new provider often takes days to weeks
- SIP / phone system: tying into existing PBXs or carrier setups
- CRM and ticketing: Zammad, TANSS, CRM Catch, and similar systems
- Custom workflows: special rules, extra languages beyond the default, edge cases
Plan support and a separate time block for those. You can still complete the first pass (agent, FAQs, test) first.
Checklist before you start the clock
With FAQs, capture fields, destination numbers or calendar access, and a clear first-line / overflow / fallback choice prepared, the session stays predictably under 30 minutes.
- Access to app.qutee.ai (invite completed)
- qutee line / telephony enabled
- Five FAQ answers + three to five required fields drafted
- Optional: Google or Microsoft calendar login or forwarding numbers
- Someone who can set the company-side call forward
Frequently asked questions
How long does setup take?
With an enabled account and a provisioned line, often about 30 minutes to a verified test call. You go customer-live once call forwarding is in place. Porting and heavy integrations extend the overall effort.
Must I change my phone number?
No. You keep your existing business number and forward it to the qutee line. Callers keep dialing the number they already know.
Do I need a new phone system?
Usually not. Many businesses start with a simple forward from their existing PBX or provider. SIP integrations are possible, but they do not belong in the 30-minute first pass.
Can I test before real customers call?
Yes. Call the test line and review everything in Calls (summary, fields, status) before you forward the company number.
Can qutee integrate with existing software?
Yes. Calendars (Google, Microsoft 365) and forwarding are often self-serve. Ticketing and CRM systems (for example Zammad, TANSS, CRM Catch) typically involve support. Overview: Integrations.
Wrap-up
In under 30 minutes you can activate an agent, load FAQs and capture, and verify a test call. Customer-facing go-live follows the number forward, often around an hour when account and line are ready.
Move fast where qutee is self-serve; loop in support for telephony and specialty integrations. Need activation help? Get in touch.
