Seldon Solutions, home Español

Engines for business

An engine runs a business process end to end, in chat.

Engines, not chatbots: each one acts on the systems behind the conversation and finishes the job. The examples below are written from Seldon’s three products.

01.1 Three written examples

Three processes, each run from the first message to the outcome.

Each example is written from one of Seldon’s products to show the shape of the work. None is a recorded conversation and none carries personal data.

A booking From Kalimba

Runs
From the guest’s request to a confirmed table.
Acts on
The venue’s book: its tables, times and capacity.
Ends with
The booking in the venue’s book, confirmed in the chat.
Written example, from Kalimba
  1. GuestDo you have a table for four on Friday at nine?
  2. EngineFriday at 21:00 is full. There is a table for four at 20:30 or at 22:00. Which one suits you?
  3. Guest22:00, please.
  4. EngineBooked: Friday at 22:00, a table for four. It is in the venue’s book; to change it, write here.
  5. OutcomeThe booking confirmed and in the venue’s book; the full slot came with two other times to choose from.

An eSIM purchase From QuiqSim

Runs
From the destination to an eSIM ready to install.
Acts on
The plans, a secure checkout link, the eSIM and its setup.
Ends with
The eSIM paid and ready to install, in the same chat.
Written example, from QuiqSim
  1. TravellerI am going to Andorra next week. Can I get mobile data?
  2. EngineYes. Here are the plans that cover Andorra. Choose one and I will send you a secure checkout link.
  3. TravellerThe first one.
  4. EngineHere is your secure checkout link. Once it is paid, the eSIM arrives in this chat with its QR code and the setup steps.
  5. OutcomeThe eSIM paid and ready to install, with its QR code and setup in the same chat.

A supplier switch From Cambialeón

Runs
From the customer’s bill to the switch request handed over.
Acts on
The bill, the offers on the market and the customer’s consent.
Ends with
The request handed over complete to the chosen supplier, with the customer’s consent. Seldon’s part ends there.
Written example, from Cambialeón
  1. CustomerHere is my electricity bill. Am I paying too much?
  2. EngineThank you. Compared like for like with your bill, these offers would cost less. Do you want the summary of one of them?
  3. CustomerYes, the first one.
  4. EngineHere is its summary. If you agree to the switch, confirm here and the request goes to that supplier, complete and with your consent.
  5. CustomerI agree.
  6. OutcomeThe request handed over to the chosen supplier, complete and with the customer’s consent. The supplier signs the contract and makes the switch.

01.2 How a build runs

Discovery, build, operate: three stages.

How a build runs, stage by stage
StageWhat happensEnds when
DiscoveryTogether we fix what the engine reads, what it does and where it hands over.The scope is agreed.
BuildSeldon builds the engine to that scope and connects it to the systems it needs.The engine goes live.
OperateSeldon runs the engine for the business, with changes as the business changes.By arrangement.

What the business gets: its engine, built to the agreed scope, and its operation by arrangement.

The three engagements

Have an engine built: write to us

04 Contact

Write to us.

Describe the process or the system, and where it stands today.

hello@seldonsolutions.es

Use the contact form

We answer by email.