The CRM that fills itself.
Every call your receptionist answers becomes a person with a timeline, and a task when someone needs calling back. Nobody at the front desk types it in.
Free while Tieloom is new. No card.
An example office, Maple Street Dental. Every name and number is invented.
Writes in from
- DDamarukaConnects today
- AAdmiralUpcoming
- CCompassUpcoming
- OOutreachUpcoming
- {Your own codeAn open API
Watch a morning fill itself.
Calls come in overnight. By the time the front desk opens Tieloom, each caller is a person, each message a task for today, and the urgent one is at the top.
From the first ring to the last follow up.
A call becomes a person
Damaruka answers, and the caller lands here: found by their number if they called before, made if they are new, with the summary, what was written down and a link to the recording on their timeline.
What needs someone today
Messages, repair requests and new client enquiries become a call back due the day they came in, urgent ones first. Tick it off and it leaves the list.
A pipeline that moves itself
Each kind of office gets the stages it uses. A booking on a call moves the person forward by itself, never backward; you move the rest with a drag.
One record for the whole desk
Owners, staff and read only seats, each signing in with their own email. Notes say who wrote them, and every stage change is on the timeline.
Three calls and a note. Written by nobody.
Ana called on Monday about whitening, again on Wednesday to ask for a cleaning, and a third time to book it. Each call hung itself on her record; the only words a person typed were the note.
- One person per phone number or email, however they reach you
- The same call sent twice is kept once
- A booking moves them along; nothing moves them back
Everything we make writes into it.
How connections work- DDamarukaConnects today
Every call your receptionist answers: who called, what they wanted, a summary, the recording link, and a task when someone needs calling back.
- AAdmiralUpcoming
Each lead from your ads, with the campaign that brought it, so you can see which campaigns bring paying customers.
- CCompassUpcoming
Companies, recruiters and applications from a job search, as a pipeline from applied to offer.
- OOutreachUpcoming
Prospects, the emails sent to them and their replies, so a sales pipeline lives here and not in sheets.
An API anyone can write to.
Your website's forms, a booking tool, a spreadsheet script: whatever can send a request can add people, timeline entries and tasks, with a key you make in Tieloom.
Read the API referencecurl https://tieloom.com/api/v1/events \
-H "Authorization: Bearer tlk_your_key" \
-H "Content-Type: application/json" \
-d '{"event": "activity.created", "id": "form-1042",
"person": {"name": "Dee Shah", "email": "dee@example.com"},
"activity": {"kind": "form", "title": "Asked for a quote"},
"task": {"title": "Send Dee a quote", "due_on": "2026-10-21"}}'Stages that fit the office.
Clinics
New patient, then Booked, then Seen, then Follow up, then Closed.
For clinics
Law firms
Inquiry, then Consultation, then Client, then Not a fit.
For law firms
Property management
New, then In progress, then Done.
For property management
Real estate
Enquiry, then Site visit, then Negotiation, then Booked, then Lost.
For real estate
Start a workspace in a minute.
Sign in with your email, choose what kind of office you run, and connect Damaruka. Free while Tieloom is new.