Customers move between channels
A question may start on WhatsApp and end in a store, so product and location context must travel.
Eyeleven / Retail
Guide product discovery, coordinate collection requests, and keep stock and exception decisions verified.

01 / Operational challenges
A question may start on WhatsApp and end in a store, so product and location context must travel.
Availability, variants, and collection timing require a current approved source.
Returns, reservations, and special requests cannot be guessed from a generic answer.
02 / Example functions
Industry-specific workflow examples. The eleven OmniForce Director templates define department responsibility; your workspace defines which tasks are enabled.
Answers approved product and store questions.
Collects item, location, and timing before a store request.
Routes stock checks and policy exceptions with context.
Explore the 11 master departments ↗ to see their responsibilities and approval boundaries.
03 / Customer journey
An illustrative workflow. No customer operation is running and no action is being sent.
A customer asks for a specific color and wants to collect it from a nearby store.
Step 01 · Customer
Identify product, variant, location, and preferred collection time.
Do not imply local stock from catalog availability.
Step 02 · Retail workflow
Use approved product and store information.
Mark stock as unverified unless a current source confirms it.
Step 03 · Workflow
Create the store request with the selected variant and timing.
Do not reserve an item without store approval.
Step 04 · Store staff
Check stock, apply policy, and communicate the valid next step.
Staff own stock and exception commitments.
04 / Capabilities and connections
Use approved product and store information.
Handle eligible customer conversations.
Create collection and stock-check requests.
Assign the relevant store and exception owner.
Available actions depend on your plan, connected tools, channel permissions and configured approval rules.
05 / Operational outcomes
The intended outcomes of a configured workflow, not measured customer results.
Product, variant, location, and timing arrive together.
Unconfirmed availability is clearly separated from current data.
Returns and special requests reach staff with the relevant policy context.
06 / Inside the OS
Keep workflow state, approved knowledge and human handoff in the same operating environment.

07 / Industry FAQ
Only when a reviewed inventory and reservation process supports that action. Otherwise it creates a request for store staff.
The workflow can explain approved policy. Exceptions and final decisions remain with authorized staff.
Your team defines the handoff conditions. When one is met, the workflow pauses and passes the conversation with its context intact.
Bring product and store information, stock access, collection rules, return policy, and store ownership paths.
Explore more
CommerceGuide decisions, continue eligible checkouts, and support customers with one supervised AI workforce.
Explore the workflow
Care & wellnessCoordinate information and appointment requests while clinical decisions remain with qualified professionals.
Explore the workflow
Property & operationsQualify intent, guide buyers through approved listings, and prepare each viewing handoff for an agent.
Explore the workflowRetail · Eyeleven AI Workforce OS
Connect its approved knowledge, define the handoff, and give your first OmniForce a clear role.