For law firms and companies that collect documents from clients

Client documents straight into your CRM

You send your client a text message with a one-time link. They photograph the contract or add a PDF on their phone, with no account and no app. Files land in the client record in your system and are deleted from updoc once you collect them.

What your client sees: your company's branding, three buttons and the link's expiry date.

How it works

Three steps from request to file in the client record

  1. 1

    A request from your system

    An agent clicks “Request documents”. Your CRM calls the updoc API and gets a link valid for as long as you set: 3 days by default, 30 at most.

  2. 2

    The client takes a photo

    They open the link from the text message, see your company's name and logo, and photograph documents or add PDFs. Up to 20 files, 25 MB each.

  3. 3

    Files in the client record

    We check every file, then send a webhook. Your system downloads the file, confirms receipt, and we delete it.

For your client

Your client needs no special skills

  • No account, no app

    The link opens in the phone's browser. Your client installs nothing and registers nowhere.

  • Works on older phones

    Safari on iOS and Chrome on Android from the last five years. The page loads without external fonts or scripts.

  • On a weak signal

    Files upload in parts. When the signal drops, the upload waits and resumes on its own. Reloading the page does not start over.

  • Your brand up front

    Your client sees your company's name, logo and colour. updoc appears only in the footer, like a payment provider in an online shop.

For developers

One request creates the link, a webhook says when files are ready

REST and JSON, key in a header. Webhooks are signed with HMAC-SHA256 and retried for at least 24 hours. You download files through the API with your key, then confirm receipt.

Events: request.opened file.ready file.rejected request.submitted request.expired file.expiring

Full API documentation (in Polish)
POST /v1/requests
Authorization: Bearer upd_live_…
Idempotency-Key: crm-42

{
  "external_ref": "kontakt-123",
  "message": "Please send your loan agreement.",
  "documents": [{"label": "Loan agreement"}]
}

201
{
  "id": "req_8Fq2Lw…",
  "url": "https://updoc.pl/Ab3…",
  "expires_at": "2026-11-21T18:00:00Z"
}

Security

What we do with your clients' files

  • Data in the EU

    Servers in Germany, files in storage under European Union jurisdiction.

  • Files deleted after collection

    Once you confirm receipt, we delete the file. A file without confirmation is deleted after 7 days, the request history after 90.

  • Every file checked

    We detect the file type from its content rather than its name and scan it with an antivirus. A PDF with JavaScript or embedded files gets a warning flag.

  • Separate infrastructure

    updoc has its own servers, database and file storage. Each part of the system has its own database permissions, and the client page has no access to any file.

Integrations

Connect updoc to the system you already use

  • VokalCRM

    Integration in progress: a “Request documents” button on the client record and files in the Documents tab.

  • Your CRM or practice system

    Through the REST API and webhooks. Test keys let you run the whole flow before going live.

Pricing

Pricing

NEED: pricing

Still collecting documents by email or messaging apps?

Let's talk about connecting updoc to your system.

NEED: kontakt