How it works
Follow one request, step by step.
Take each step yourself. Nothing is sent.
Try the concierge
Pick a request, then take each step yourself.
The demo needs JavaScript. How it works describes each step.
Step 1 of 7Monday, 08:12
Ask for a result, in your words.
Pick a request, or describe one of your own.
On screen: a new, empty request.
Illustrative example. No email is sent. This example follows a set script. Shown in the iPhone app, which is not on the App Store.
What was recorded
A plain-words selection of the entries recorded for this request. Illustrative example.
- Mon 08:12
Request captured.
5a7d3e…c90b14
- Mon 08:12
Claire Martin handed the request to the concierge.
4e1c07…a39b52
- Mon 08:12
Hand-over recorded: it may write only to , six emails at most, for seven days.
9d2f61…07c8e4
- Mon 08:12
Question asked:
b37a90…5e1d26
- Mon 08:13
Claire Martin answered: .
0c84de…f2a917
- Mon 08:13
Email planned to .
6f19b3…c40d88
- Mon 08:13
Recipient, count and expiry checked against the hand-over.
e25a7c…19b3f0
- Mon 08:14
Sending rules checked.
18d6f4…7a2c65
- Mon 08:14
Checked again just before sending.
a90b2e…d61f34
- Mon 08:14
Accepted by the sending service.
53c8e1…0b97ad
- Mon 08:14
Waiting for a reply.
cf4a26…8e5301
- Tue 08:16
Follow-up 1 of 2 planned.
72e9d0…4c1fb7
- Tue 08:16
Recipient, count and expiry checked against the hand-over.
3b06a8…e97d42
- Tue 08:16
Sending rules checked.
d8f153…26a0c9
- Tue 08:16
Checked again just before sending.
61a4c7…b3e8f5
- Tue 08:16
Accepted by the sending service.
9e3d20…5f71ca
- Tue 08:16
Waiting for a reply.
20b7f9…a84e16
- Tue 10:41
Reply received from . (Illustrative: replies have not yet been tested with a real supplier.)
c5e812…3d09b7
- Tue 10:42
Outcome recorded.
87fa4d…61c2e0
These entries cannot be edited. Each is linked to the entry recorded before it in your workspace’s record, and each night the record is signed if it passes its check.
Step {n} of 7
Monday, 08:12
Monday, 08:13
Monday, 08:14
Tuesday, 08:16
Tuesday, 10:41
Tuesday, 10:42
Handing over is your go-ahead.
It asks instead of guessing.
It writes and sends the email straight away.
No reply, so it follows up.
The supplier replies.
The outcome comes back to you.
Each step is recorded.
Hand over your own requests.
Nothing is sent before you hand it over. After that, within these limits, you do not approve each email.
Thursday
Saturday
Friday
“{wd}” could mean two days, so it asks you, and sends nothing until you answer.
It goes from a Lorne & Vale address, not from your mailbox. Sent means the sending service accepted it.
24 hours after its email, with no reply recorded, it sends a follow-up that quotes the original. Weekends included.
A reply from the address it wrote to, if it passes the sender’s email authentication, is designed to come back into the request.
It reports what the supplier said, not that the delivery happened.
It reports what the supplier said, not that the service took place.
A request is designed to close only once its outcome is recorded, and you receive an email when it does. {tail}
Your request, the authority it gives, each question and answer, each check before sending, each email the sending service accepted, and each wait for a reply.
Your example comes with you: it fills in the first task on the form, and you can change it or clear it.
On screen: your request, ready to hand over: {req}
On screen: the concierge asks: {q}
On screen: the email it sent on Monday at 08:14. From: Lorne & Vale, intake@mail.lornevale.com. To: {addr}. Subject: {subj}. {body} Status: waiting for a reply.
On screen: the request, waiting for a reply after follow-up 1 of 2.
On screen: the request, in progress. A reply was received. The concierge is assessing whether it resolves the request.
On screen: the request, completed. {out}
On screen: the completed request.
It may write only to {addr}.
Email sent to {addr} and accepted by the sending service. Waiting for a reply.
Tuesday, 08:16. No reply was recorded, so follow-up 1 of 2 went to {addr}. Subject: Follow-up: {subj}.
Tuesday, 10:41. A reply arrived from {addr}. The concierge is assessing it.
Tuesday, 10:42. Request completed. {out}
19 entries shown.
Enter an email address in the format name@company.com.
Writes only to: {addr}
Six emails at most, within seven days
Anything that would commit you, such as a price, a booking or a contract, is designed to come back to you
You can pause or cancel it until it ends
This example follows a set script, so it continues with {chip}. Your own words are kept for the invitation form.
No reply after a day: a follow-up. At most two, then it asks you.
Next: {t}
See what was recorded
Follow-up 1 of 2 to {addr}
“Follow-up: {subj}”
“I’m following up on the message below. Could you let us know where the request stands or when we can expect your reply?”
In this example the supplier answers. Replies have not yet been tested with a real supplier.
“{reply}”
From {sup}, Tuesday 10:41
Email to Claire Martin
“Your request is complete: {title}”
Blanchisserie Morel
Atelier Lemaire
Thermo Services
blanchisserie.morel@example.com
atelier.lemaire@example.com
thermo.services@example.com
Confirm Thursday’s linen delivery with Blanchisserie Morel, {addr}, and follow up if they do not answer.
Email Atelier Lemaire, {addr}, to confirm the flowers for Saturday’s wedding, and follow up if they do not answer.
Ask Thermo Services, {addr}, to confirm Friday’s boiler service and the time their engineer arrives, and follow up if they do not answer.
Confirm Thursday’s linen delivery with Blanchisserie Morel
Confirm Saturday’s wedding flowers with Atelier Lemaire
Confirm Friday’s boiler service with Thermo Services
The email to {sup} is ready to write once the day is clear.
An email went to Blanchisserie Morel to confirm {day}’s delivery.
An email went to Atelier Lemaire to confirm the flowers for {day}.
An email went to Thermo Services to confirm {day}’s boiler service.
This Thursday or next Thursday?
This Saturday or next Saturday?
This Friday or next Friday?
This Thursday
Next Thursday
This Saturday
Next Saturday
This Friday
Next Friday
Email Blanchisserie Morel to confirm Thursday’s delivery
Email Atelier Lemaire to confirm Saturday’s flowers
Email Thermo Services to confirm Friday’s boiler service
Linen delivery {day}
Wedding flowers {day}
Boiler service {day}
Could you confirm {day}’s linen delivery to The Linden House, and the time you expect to arrive?
Could you confirm the flowers for the wedding at The Linden House {day}, and the time you plan to deliver them?
Could you confirm {day}’s boiler service at The Linden House, and the time your engineer expects to arrive?
Hello,
{line}
Kind regards,
Lorne & Vale
Good morning. Yes, confirmed: we will deliver {day} from 07:00 to 09:00.
Hello. All confirmed for {day}: we will deliver the flowers at 10:00.
Hello. {Day} is confirmed: our engineer arrives at 09:00.
Blanchisserie Morel confirmed the delivery for {day}, from 07:00 to 09:00.
Atelier Lemaire confirmed {day}’s flowers, with delivery at 10:00.
Thermo Services confirmed {day}’s boiler service, with the engineer arriving at 09:00.
Obtain the reply to the request
Report the actual outcome
Follow up for the response (1/2)
The sending service accepted the message.
I’m watching for replies and progress.
Follow-up resumes automatically at the next check.
A reply was received. I’m assessing whether it resolves the request or requires more work.
Lorne & Vale <intake@mail.lornevale.com>
Accepted by provider
resend · 0f3a…
Monday 08:12
Monday 08:13
Monday 08:14
Monday 08:19
Tuesday 08:16
Tuesday 08:21
Tuesday 10:41
Tuesday 10:42
Close
New request
YOUR WORK CONCIERGE
What can I take off your hands?
Ask a question or describe what you need done…
Describe the result you want
Delegate this task
Saving your request
Follow every step. Answer only when needed. Pause at any time.
Request
Just what’s needed
Only the details needed to continue.
Enter a different answer
Continue with these details
Progress and steps
Waiting for a response
Your concierge is working
Steps done
33%
50%
Completed steps
Waiting steps
Upcoming steps
What happens next
Next check {t}
Step by step
{a} of {b}
Completed
Request outcome
Review action
Send email
Recorded result
Exact action
Message
Recipient
Sender
Subject
lornevale-platform.com
LV
Overview
Requests
Detail
EN
FR
My requests
CONCIERGE REQUEST · THE LINDEN HOUSE
Lorne & Vale
Your answer is needed
Waiting for a reply
In progress
Completed
Next check: {t}
To continue
Reply to the concierge
Reply and continue
Pending
Waiting
Done
Operations and evidence
Result recorded
This receipt does not establish physical completion.
Action timeline
Question asked
Request handed to the concierge
Your answer recorded
Work in progress
Waiting for a reply
Reply received
Outcome recorded
What needs taking care of?
Describe the outcome you need and what you already know…
Save request
Saving…
In detail
The rules behind each step.
-
Handing it over
Handing over a request is your go-ahead to email the addresses written in it or in your answers, at most six emails over seven days.
Before each email, the database checks the recipient, the count, the expiry and the role of the person who handed it over. Only an owner, an admin or a manager can hand over email. For anyone else’s request, no email is sent.
You do not approve each email. The limits above apply instead. Anything that would commit you, such as accepting a price, a booking or a contract, is designed to wait for your approval of that exact email.
-
The question
When something essential is missing, such as the supplier’s email address or which date you mean, it asks you instead of guessing, and sends nothing until you answer.
It asks only what it needs to continue, never more than three questions at a time. When a request needs your answer, Lorne & Vale tells you by email.
-
Sending
Once it has what it needs, it writes and sends the email straight away. Emails go out from a Lorne & Vale address, not from your own mailbox. It writes in the language you use in the app, English or French.
Sent means the sending service accepted the message. Lorne & Vale does not track whether it was opened. Each email it sent can be read word for word in the request.
-
Follow-ups
If no reply is recorded 24 hours after its last email, it follows up, at most twice. Then it stops and asks you how to proceed. To write to someone else, you hand over a new request.
It keeps working when you close the app. Follow-ups run on our servers, weekends included.
The follow-up email, with an example subject. The original message is quoted below it. Follow-up: Linen delivery this Thursday
Hello,
I’m following up on the message below. Could you let us know where the request stands or when we can expect your reply?
Thank you.
-
Replies
Replies are designed to come back into the request when they come from the address it wrote to and pass the sender’s email authentication. This has not yet been tested with a real supplier. Until it has, a reply can be missed and a follow-up can still go out.
It only picks up a reply from the address it wrote to. If the supplier answers from another address, you can pause or cancel the request.
-
Closing
A request is designed to close only once its outcome is recorded, and you receive an email when it does.
The person who made a request can pause, resume or cancel it until it ends. Emails already sent stay sent.
What it cannot do
- It cannot book, pay, order, make phone calls or manage your calendar. When a request needs one of those, it stops and tells you what is left for you to do.
- It works by email. It does not send texts or use messaging apps.
- Lorne & Vale does not connect to Gmail, Outlook or Google Calendar, and sends no push notifications.
- An email already sent cannot be recalled.
The record
Every step, on the record.
Every step is written to a tamper-evident record. Each workspace has its own chain, and every entry carries the SHA-256 fingerprint of the one before it.
Each step is recorded: your request, the authority it gives, each question and answer, each check before sending, each email the sending service accepted, and each wait for a reply. Entries are append-only: the service does not allow them to be changed, and no job deletes them.
Each night, when your workspace’s record passes its check, its latest entry is signed. If the record fails its check, nothing is signed and owners are told in the app. Owners and admins can see in the web app whether the latest signature passed our server’s check.
What would you hand over first?
Once we approve your address, you create your account and name your workspace.