Conversational access and explanation

Ask the question. See the context behind the answer.

Ask Viq helps commerce teams explore connected findings, understand diagnoses and review recommended next steps in plain language.

See Ask Viq in the tour See the four pillars Browse questions and tasks

The crews that use it

Ask Viq is how you talk to every crew.

Ask Viq is how you talk to a crew. Open any finding and chat with the lead who raised it: ask why, change the scope, or edit the ticket before sending it to Development.

Pulse crewStore Health

Chat with the Health Lead on any finding. Edit the ticket before sending it to Development.

Finds

Beacon crewSEO and AI Visibility

Chat with the Beacon lead about any product, page or brief.

Optimises

Compass crewAds Performance

Chat with the Compass lead about a campaign or budget call.

Grows

Prism crewStore Experience

Chat with Prism about a run or a failed case.

Tests

CodeCraft crewStore Development

Crew discussion on hard cases. A needs-input panel with a CSV when it cannot proceed.

Fixes

Bridge crewMigration and Recovery

Migration and restore status, in plain English.

Protects

What you can ask

Move from a broad question to a reviewable finding.

What changed?

Summarise relevant findings from the connected sources available to the workflow.

Why might it matter?

Explain the diagnosis, evidence and limitations supplied by Vortex Mind.

What should we review next?

Present prioritised recommendations and the owner or approval path where configured.

Clear product boundaries

Ask Viq explains the work. It does not deploy it.

Vortex Agents owns bounded execution. Vortex Apps owns staging, backup and rollback for supported workflows. Vortex Memory owns retained context and outcomes.

See how approved work is executed

Start with a real finding

Run a free audit, then explore the context.

Run a free audit Book a walkthrough