Solutions · Sectors · Retail and wholesale
The customer is at the counter. The answer does not depend on the shift.
Skyller publishes the chain's rule once and answers at the counter with the document alongside, the same in every store; expired campaigns and price lists drop out of the answer on their own. The exception becomes a card with an owner and a due date for whoever decides.
- The same rule in every store
- Promotions within their validity
- Retail profiles
- Exceptions with an owner and a due date
Skyller - AI AssistantReturn · store serviceA customer wants a return after 45 days without packaging. Where can I check the rule?
Skyller is an AI and can make mistakes. Remember to check.
Demonstration · illustrative data
Who works here
From head office to customer service.
Consistent answers
How it works today
Asks the colleague next door, and the answer changes with whoever replies; when nobody knows, they call head office and the customer waits.
With Skyller
Asks in the chat and gets the answer with the chain's document alongside, effective date visible.
Focus on exceptions
How it works today
Repeats the same explanation to every new person and becomes the team's phone line whenever an exception comes up.
With Skyller
Publishes the rule once and gets the exception as a card with an owner and a due date.
Information for the shop floor
How it works today
Keeps datasheets, supplier price lists and warranty policies in a folder only they can open.
With Skyller
Uploads the supplier's material to the purchasing workspace and it starts answering, scanned PDFs included.
Current terms
How it works today
Works from the price list downloaded last week and finds out late that the terms changed.
With Skyller
Checks the current terms from their phone; the expired price list has already left the answers.
The routine of the people who sell
Where Skyller comes in — and what stays with the team.
Select a routine to see the details.
Skyller does it
The returns and warranty rule
The Warranty and Returns Policy and the Returns and Exchanges Process start from ready-made templates in Portuguese, go through review and are published. Whoever is serving asks in the chat and gets the answer with the document alongside, to check the source before speaking to the customer.
Supplier material and rules
Datasheets, manuals, price lists and warranty terms come in any format, and anything scanned goes through OCR. The Purchasing and Procurement Policy, the Supplier Quotation and Selection Process and the Supplier Code of Conduct answer what to attach and who authorises; the negotiation stays with the buyer.
Campaigns and price lists with an end date
Every document carries an effective date and an expiry date; once expired, it stops answering, and nobody offers a finished promotion by mistake.
The exception that needs authorisation
A case outside the policy becomes a card with store, customer, reason and owner, with a reminder 24 hours before the due date and on the day. The manager is still the one who authorises.
New people on the shop floor
The published text produces an assessment of 3 to 20 questions, assigned to people and teams with a deadline, with each person's result.
Depends on configuration
Stock counts and out-of-stocks
Stock Management and the Physical Inventory Process become published procedures, and the count can become a Kanban with stages, owners and due dates. The physical check and the adjustment in the system stay with the team.
The store system and the online shop
The catalogue carries ready-made commerce and spreadsheet connections. A point of sale or ERP outside the catalogue comes in through the address of a bridge, with a secure connection and function-by-function enabling, built by the vendor, your IT, a partner or Skyller as a separate service.
Stays with the team
Selling, charging and writing off
The price actually charged, stock balances, invoicing, authorising the exchange and the money in the till stay in your system, with your team.
Return requests
Under review1
Return · Aurora
HighRequest reason
DocsAssigned to owner0
Demonstration · illustrative data
Live proof
Saturday, 11:40. A return outside the window and a queue behind it.
Starting point
A customer wants to exchange a product bought 45 days ago, without the packaging. The assistant joined three weeks ago, and the policy is a PDF that circulated by email in May.
What happens
- Operations picks the Warranty and Returns Policy in the library, which already carries the company name, the owner and the date, adjusts the chain's windows and sends it for review; whoever wrote it does not review their own text, and the regional manager reviews it on her phone and publishes.
- At the counter, the assistant asks from her phone whether an exchange without packaging, after 30 days, has an exception. The answer arrives with the policy alongside, with type, owner and effective date; the May version no longer answers.
- The case is an exception. At the assistant's request, Skyller opens a card on the authorisations Kanban with the store, the customer, the reason and today's due date, and the regional manager gets the reminder and decides.
Result
The customer hears the same answer she would get in any store of the chain, and the exception becomes a request with an owner and a due date; an authorised exchange is recorded in the store system by the team.
Good to know
- Invoices, stock balances and the price actually charged stay in your sales system; Skyller answers from what the chain published.
- Authorising the exchange, refunding, invoicing and moving money in the till stay with the team, in the store system.
Fictional chain, customer and due date; real product features.
Features
What supports the chain's routine.
Select a feature to see how it works.
One published rule, and it is the one that answers
The chain decides which document types require review and approval. There, whoever wrote the text does not review it, and approval belongs to whoever was given that responsibility, not to someone who merely holds an administrator profile. Drafts and documents under review do not answer; the previous version is kept.
An expiry date that pulls the campaign out of the answer
Price lists, campaigns, commercial terms and warranty statements carry effective and expiry dates; once the expiry passes, the document leaves the answers. The periodic review only flags that it is time to reread.
Templates in Portuguese for the chain's rule
The Warranty and Returns Policy, the Returns and Exchanges Process, Stock Management, the Physical Inventory Process, the Sales Manual, Customer Service Excellence, the Purchasing and Procurement Policy and the Supplier Code of Conduct, on every plan. Skyller fills in company, owner and date; anything missing stays as a field to complete.
Supplier material, in any format
PDF, Word, PowerPoint, Excel, CSV, HTML, text, scanned image and audio. A scanned datasheet goes through OCR before becoming searchable text, and the file enters the workspace with a type, an owner and a date.
Sector profiles ready to install
Store Manager, Inventory and Stock Analyst, Pricing Analyst and Purchasing Analyst sit in the agent library, filterable by Segment. Anyone who is not view-only installs one and uses it as it is, or duplicates it to create their own version.
The exception with an owner, a stage and a due date
You build the Kanban with the chain's own fields (store, customer, reason, amount, owner) from 23 field types, and a field made mandatory at a stage stops the card from advancing without the evidence. The reminder goes out 24 hours before the due date and on the day to whoever is on the card.
The question that sweeps the Kanban
«What is overdue?», «what is with the Centro store?», «what is stuck at review?»: Skyller reads the Kanban by stage, owner and overdue date and returns the list, respecting the configured visibility. It counts cards; adding up amounts stays with the spreadsheet or the system.
Training whoever started this week
The published text produces an assessment of 3 to 20 questions, with 2 to 6 options and a pass mark set by the chain, assigned to people and teams with a deadline. Each person gets the reminder, with no certificate, course path or automatic chasing.
How to start
Start with one question, not with the whole chain.
Pick the question that most often makes a store call head office, publish its answer and let the counter test it, with no project.
Operations
Creates the chain's hub with one workspace for the rule that applies in every store and another for purchasing and suppliers, defining who joins each.
Operations
Picks the Warranty and Returns Policy in the library and adjusts windows, exceptions and who authorises each one.
Regional management
Reviews and publishes; from then on, that policy is what answers when somebody asks at the counter.
Store
Asks in the chat while serving and checks the answer against the document opened alongside.
Operations
Builds the exceptions Kanban with the chain's fields and turns on due dates, so the request stops living in a conversation.
Store questions
The doubts before the first store goes into Skyller.
Start with one question
Publish the returns rule. Let the counter ask.
Create your account, publish the policy that most often makes a store call head office and ask three sales assistants to ask from their phones during the shift.