Signed on site. Even offline.

Yes. With no signal, the technician previews the document in the Field Service mobile app, answers its questions, signs and taps Submit. On sync, Docable makes the PDF, Word file or both and files it on the work order.

Generate Service Document lists up to 25 documents from the last sync. Preview shows an example filled from what the phone holds, photos included. The technician answers, signs and taps Submit; the file is made on sync.

The Salesforce Field Service mobile app on iPhone and Android, online and offline. The Salesforce mobile app has Docable's Generate Document action too, while connected.

One org setting, two permissions and a Docable role for each technician, and the action on the layout. Docable Setup checks it all and says what to fix.

Any object, standard or custom: Work Order, Work Order Line Item, Service Appointment, Asset, Maintenance Plan, Time Sheet and the rest. The document is filed on the record the technician is on: one per boiler, per visit or per job.

They see only the templates on that object offered for that job. Each template's Offer when rule decides, from any field of the record, its lookups or the account: a gas safety record only on an annual service.

Up to four per template, by type: Customer, Technician, Engineer, Witness, as your org names them. Each is drawn on a full-screen pad, printed with the name and date, and stored as a Digital Signature. Your own can be saved.

They pick a reason from your own list, set in Salesforce Setup, with a note if you ask. It prints in the document; a sample Flow copies it to a Task. You choose which signature types allow it.

Yes. A section, table or line can show only when a condition holds, such as an appliance failing or a field being filled in, and blank values can hide themselves. One template covers every variant.

Yes, for what the job form can't hold, such as a reading nobody stores. Text, number, date, yes or no, a choice; required ones before Submit; offline too, checked on sync. Most templates ask nothing.

Yes. Generate Service Document is a Lightning quick action: an admin drops it into a Guided Experience step as a card, required or optional. The technician makes, signs and submits the document in the path, online or offline.

Yes. A visit pack in Docable Setup groups two to six templates on one object, such as the service report, gas safety record and invoice: one signing, one PDF, offered first on the phone, online and offline.

Yes, as galleries of the record's photos by title. Photos taken before Submit are in the document made on sync, even if still uploading; a photo taken after Submit goes in the next one.

On the record, under Files: PDF, editable Word or both, named as the template says. Optionally also SharePoint, Google Drive or Amazon S3, through a storage destination your admin connects.

Yes, by Flow: a record-triggered Flow emails the signed report the moment it is made, and Docable ships a sample to copy. Emailing is done by Flow, not from the sign step.

Docable retries for about forty minutes, with the signatures kept. If it still can't, the technician gets a Salesforce notification that opens the record with the reason.

They come with Field Service and do a standard signed report well. Docable adds a Word-like editor, Brand Kits, photo galleries, conditional sections, any object, phone questions, visit packs, PDF and editable Word, bulk runs, and the office's documents.

Yes. Docable runs from Flow, so a record-triggered Flow can make the document when the work order closes, file it on the record and email it. Salesforce's own Create Service Report action can't start from a flow.

Yes. Docable adds its own action to the layout and changes nothing about Service Reports or Document Builder. Use both while you move across.

No. Docable is its own package and makes every document with its own code inside your org.

No. The same editor makes documents on any object, for every team. Field Service is where Docable starts.

No. An admin builds templates in the editor and adds the action to the layout; Docable Setup checks the org and each technician.

30 field service starters, listed above: from the appointment confirmation and job sheet to the gas safety record, PAT test record, refrigerant record and water hygiene log. Have statutory wording reviewed.

Minutes. Describe it; AI drafts it with fields, galleries, conditions and brand placed: in Build with AI, an Agentforce agent, or Claude on Docable's MCP server. A person proves it on a real job and makes it live.

Yes, in the background from a list, a Flow, a schedule, Apex or REST, filed on each record, with one combined PDF if you want it. No per-document fee.

No. Every document is made inside your org by Docable's own code, as the person who asks, with their permissions. Nothing leaves unless your admin connects a storage destination or a data provider. The AI never sees your records' values.

£399 (or US$499) a month per production org: any number of technicians and documents, every sandbox included.

Not yet. Docable is a member of the Salesforce Partner Program, on its way to the AppExchange. Join the waitlist to hear first and be first to install.