Frequently Asked Questions

Customers can reach the voice agent by phone or submit a report through a web form. Both channels feed into the same structured flow, so your team receives consistent information either way. That keeps the experience flexible for end users without forcing you to maintain two separate processes.

The report is pre-sorted automatically: problem type and urgency are detected and turned into a clear summary. A structured email or ticket is generated with the key facts so your team can prioritize and respond immediately. Critical cases can be highlighted so nothing gets lost during busy periods.

We typically capture name and contact details, the affected location or machine, problem type, a timestamp and an assessed priority. Where refunds are involved, payment details such as IBAN or PayPal can be added. The goal is to give support everything they need without chasing the customer for basics.

The AI acts as the digital front desk: it structures unstructured calls and form entries, maps them to useful categories and estimates urgency. It prepares data so your inbox or ticketing system shows at a glance what happened. It deliberately does not decide refunds or on-site actions, those remain with you.

All commercial and customer-facing decisions stay with you: whether to refund, call back, offer goodwill and what action to take on site. OUTAG3 delivers solid preparation with context and priority but does not replace operational or compliance judgment. You stay in control and use AI as an accelerator, not a substitute for responsibility.

No. Day to day your team works with normal emails or tickets written in plain language about what happened. Nobody needs to write prompts or operate a special AI tool. Technical topics like webhooks or APIs mainly come up during setup and can be clarified in onboarding.

Typical cases fit well: money taken without product, product stuck in the chute, card payment failures or unclear age verification. Recurring reader or dispensing issues at one site map cleanly too. If your scenario does not match standard categories, we can tailor categories and rules to your operation.

Priority combines problem type and report content, for example how much revenue or customer satisfaction is at stake. That separates minor issues from real emergencies without your team rating every call manually. Especially important cases can be highlighted or marked for immediate handling.

Yes. You define how urgent each incident type is at each location, e.g. card reader outage as high and small amounts as normal priority. Rules can reflect your real operations and be refined after the pilot. Automatic triage then matches your internal escalation logic.

Yes. Categories, labels and mappings can match your machines, product groups and internal reporting. That also helps later analysis because reports land in your language, not generic defaults. Together with priority rules you get a picture that fits your business.

Whenever a case is unclear in content, touches sensitive topics or automatic classification seems uncertain, it is flagged for manual review. Your team then sees explicitly that human judgment is needed. That keeps quality high without hand-checking every small item.

A focused pilot can often go live within a few days once basics are in place, such as phone number, forwarding and initial categories. Exact timing depends on whether you start with web form, phone or both and how quickly approvals happen on your side. After you join the waitlist, we align the fastest path for your first location once early-tester spots open up.

You start with one location, agreed categories and fixed escalation rules so everyone knows when and how to react. Over two to four weeks you collect real reports; we tune recognition, priority and output wording from that data. At the end you have evidence whether the flow fits your day-to-day and what to adjust before wider rollout.

Your website request is accepted through a protected form and passed to the OUTAG3 team. It stays separate from the later complaint intake used by your customers. We use the information to clarify your goal, first location and a realistic pilot scope with you.

Yes. Incoming reports can be handed off by email, webhook or API into your existing ticketing, mail or CRM stack. Many teams start with email and deepen integration once the process is stable. The idea is that OUTAG3 handles first contact while your established workflows keep running.

Join the waitlist. We are gathering early testers and cannot commit to a fixed testing window yet—when onboarding opens, we will follow up with next steps (pilot scope, initial categories, realistic start for your first location).

Yes. For operators with multiple brands, franchise structures or strict internal rules, separate storage per customer or tenant is supported. Configuration and data stay logically isolated. We align details with your requirements in the project.

We follow data minimization, purpose limitation and traceable processing, with controlled access to data. On request, retention periods can be defined per data type so you can meet deletion and documentation duties. Full detail is in our privacy policy.

Privacy-compliant use is generally possible when roles, retention and data processing agreements are set correctly and you meet your obligations as controller. OUTAG3 supports this with clear processes and configuration options but is not a substitute for legal advice. Involve your privacy specialist when in doubt.

Specific processing locations and subprocessors depend on the chosen infrastructure and connected partners, e.g. for hosting or telephony. Only data needed for intake, classification and handoff to you is processed. Regions and subprocessors are described in the privacy policy.

Critical reports are marked immediately and delivered through the alert channel you define, e.g. in addition to normal email or by SMS depending on setup. That makes it visible when a card reader fails during peak hours or another revenue-critical incident occurs. You set the exact escalation chain in the pilot.

Yes. Reports can be analyzed by category, location and time window to spot patterns like repeated dispensing faults or reader issues. That helps fix root causes before the same machine consumes support every week. Depending on your plan, reporting, history or regular summaries are available.

For spikes we use technical safeguards such as rate limiting and clear fallbacks so the system stays controlled under many parallel requests. That discourages abuse and protects handling quality. Legitimate customers usually notice no difference in normal operation.

Yes. The usual path is a pilot at one site followed by rollout to more locations without reinventing the core process each time. Categories and rules can be reused across sites or customized per location. Support scales with you instead of starting from scratch.

Useful metrics include response time to reports, share of cases pre-sorted without follow-up, frequency of critical escalations and time saved in support. Comparing before and after makes the impact obvious. In the pilot we can define which metrics matter most for you.

Yes. OUTAG3 sits at the front and structures incoming complaints while your existing ticket, email or CRM processes continue unchanged or with light adaptation behind it. You do not need to overhaul everything to benefit from automated intake. You deepen integration once the flow is proven.