Member marketing and service tickets
- Type
- Demonstration project
- Project
- Omnichannel retail demonstration project
- Industry
- Retail
The scenario and numbers in this demonstration project are simulated data.
- Industry
- Retail
- What was built
- Agents, a semantic model, query tools and write tools, built on demonstration data
- Where the knowledge came from
- Demonstration data in a retail database: products, stores, logistics, members and service tickets
Lists to follow up
- Member marketing needs the customers who abandoned a cart and can still be won back.
- The customer service supervisor needs the tickets at SLA risk.
Retail database and queries
- This demonstration project has a semantic model on the retail database.
- The agents use query APIs to check best sellers, channel and store KPIs, low-stock SKUs and parcels with delivery exceptions.
Agents and tools
- Operations overview, stock allocation, logistics fulfilment, member marketing and service tickets each have their own agent.
- Each agent queries data with the query tools for its own area.
- The member marketing agent uses write tools to create coupons and member segments.
- The stock allocation agent uses write tools to create stock transfer orders.
- The service ticket agent uses write tools to escalate service tickets.
Continuous improvement
- At retailers like this, new coupons and member segments will keep being added.
- The agents will collect feedback on their answers from users. The feedback will go to Odin.
- Wrong answers will become tests. A change will be kept only if scores improve.
Get started
Book a two-hour workshop
AI feasibility review of a live workflow