Skip to main content

Product guide 01 / Qfix Connect & Screen

Qfix Connect and Screen. Know the scope.

Two products, two working environments: customer operations on the phone and technical support on a shared screen. This guide explains what each product does, how they differ and what must be confirmed before rollout.

Last updated: Plain-text version

Qfix Connect

Qfix Connect is an AI voice customer operations product that connects to a company's existing phone line. It manages inbound and outbound calls in natural conversation, provides technical support within a defined scope, hands off to a human when needed, creates support tickets and calls the customer after service to confirm the outcome.

Used in existing customer operations; the scope of each new deployment is confirmed separately.

Explore the product experience

Qfix Screen

Qfix Screen adds visual context to technical support by seeing a user's shared screen. Voice guidance and specialist assistance help the user progress on screen. It is a separate screen-support experience, not the name of Connect's call analytics dashboard.

In pilot with existing customers in Türkiye. Authorized clicking and typing on screen are beta features, not generally available unrestricted autonomous computer control.

Explore the product experience

Compare the two products

ScopeQfix ConnectQfix Screen
Working environmentInbound and outbound calls on an existing phone lineTechnical support on a screen shared by the user
Core workflowAnswer → support or hand off → record → call back and confirm → close or reopenSee the screen → guide by voice → involve a specialist when needed
Human controlContext-aware handoff at scope or authority boundariesSpecialist assistance; permissions and beta scope for screen actions
Getting startedPhone, knowledge and business-system connections verified during setupPilot with existing customers in Türkiye; suitability and permissions reviewed together
01

Who is it for?

Connect is evaluated for support work that begins with a phone call, becomes a record and requires follow-up. Software and POS support, MSPs and technical service operations are priority examples. Inbound support, callbacks, post-service confirmation and payment reminders are separate workflows.

Screen is evaluated for technical support where seeing the issue is more useful than describing it. Call operations and screen support are scoped separately.

02

What is needed to get started?

For Connect, define the existing phone line and access/routing method, authorized knowledge sources, working hours, handoff rules and ticket fields. Start a pilot with one workflow and agreed evaluation criteria.

CRM or ticket-system connections are verified during setup after reviewing API access, permissions and required actions. Third-party logos on the site do not mean every connector is ready or live, or imply partnership or certification.

For Screen, confirm pilot eligibility, screen sharing, specialist support and authorized beta actions. This guide is not private API documentation or a promise of compatibility with every device; technical requirements are confirmed for each deployment.

03

Languages and demonstrations

The website includes Turkish, French and Darija Connect audio samples. They are scripted dramatizations, not actual customer calls or evidence of live success rates. Production language scope is verified for the scenario and deployment; a sample does not establish general availability in a language.

The Screen example includes Turkish voice guidance. Its interactive Wi-Fi scene uses illustrative data, does not connect to the visitor's device and does not change real network settings. Product films are also illustrative.

04

What should you confirm before purchasing?

Review phone infrastructure, integration scope, language, expected traffic, knowledge sources, handoff and follow-up rules together. Pricing and commercial scope are confirmed in discussion; this guide makes no price or SLA commitment.

Recording/transcript processing, retention, access permissions, hosting, required agreements and security requirements must be confirmed for the deployment. The website privacy notice alone is not a product data-processing agreement or security certification.

05

About Qfix

This guide describes Qfix Connect and Qfix Screen at qfix.ai. Qfix is a Vox Technologies brand and should not be confused with other companies or products sharing the name. Contact hello@qfix.ai for product and deployment questions.