Documents & e-sign
Nobody has to leave the conversation to sign anything.
The quote goes out on the number they text you on, then comes back signed.
100%
of the paperwork ends up in the customer’s record — the quote, the signature and the call that agreed the price.
0logins
for the customer: no account, no app, no printer, no second tab.
None
filing afterwards, because the signed copy is in the record the moment it comes back.
From the call that agreed it to the signed copy
Against how paperwork normally travels
| How it normally works |  With qallin | |
|---|---|---|
| How it is sent | Emailed from a signing tool | A message on the number they call |
| Who it comes from | A sender address they do not recognize | The same thread as the calls |
| Where it is signed | On a signing site, in another tab | From the message, on their phone |
| The signed copy | Downloaded, renamed and filed by hand | Already in the customer’s record |
| Chasing it | Reminders from a tool with no context | A follow-up on the conversation itself |
| Finding it in a year | In the signing account, searched by name | Under the customer, with the calls |
| What the phone system knows | Nothing — the two never meet | Both halves, in one timeline |
What the documents module does
Sent on the line
The quote leaves as a message on the business number rather than out of somebody’s inbox.
Signed on a phone
Opened from the message, signed with a finger — no account, no app, no printer.
Filed where it happened
The signed copy lands in the customer’s record beside the calls, texts and notes.
What gets recorded
The document, who signed it and when, kept with the conversation it came out of.
The chase is drafted
When it goes quiet, the reminder is already written on the thread for someone to send.
It belongs to the business
Anyone with access to that customer can find it, including the person who takes over.
Straight answers
A signature here is captured, not certified. We record what was signed, by whom and when, and keep it with the conversation. Whether that satisfies the rules that apply to your kind of agreement — mandatory clauses, a rescission notice, a wet signature, an identity check — is a question for your own counsel, and some places are strict about it.
The paperwork that comes out of a phone call: a quote, an estimate, an agreement, an authorization to proceed. If you already have the document, you send that. The module is not trying to be the place your contracts are drafted — it is the place they are sent from and the place they come back to.
No, and that is most of the point. They get a message on the number they have been calling, open it on the phone in their hand, and sign. Nothing to install, nothing to register for, and no email address that turns out to belong to a spouse who has not been on any of the calls.
Yes. It goes out of the record you have open in front of you, which is the same record the call is in, so the customer can be looking at it before you say goodbye. That is usually the difference between a document that gets signed and one that gets thought about.
In the customer’s thread, as an entry directly above the call that agreed it, and you can download it whenever you want a copy of your own. It sits in the same timeline as everything else that has happened with that customer, so nobody has to remember which tool a job was signed in.
It stays an open commitment rather than a document rotting in a tool nobody logs into. The follow-up is drafted on the same thread, on the same number, so the next person to look at that customer can see there is an unsigned quote and one message to send about it.