docstoc documentation

Getting started

1. Open the docstoc tool — no signup required for the free tier.
2. Add invoices manually (client, amount, due date) or upload a CSV export from your accounting software.
3. Click Draft chase to generate a tone-matched follow-up email.
4. Copy the draft into your email client or open the mailto link. docstoc never sends on your behalf.
5. Mark the invoice paid when it clears, or schedule your next reminder.

Free includes 5 AI drafts per month with no account. Pro ($14.99/mo) removes the cap and unlocks tone tools, chase plans, connectors, branding, webhooks, and the API. Business ($39.99/mo) adds reply detection, risk scoring, demand letters, evidence packs, certificate branding, and SSL automation.

Tone tools

Every draft can be rewritten in one click from the invoice card, on Solo and up:

• Soften — less pressure, still asks for payment.
• Firm up — clearer urgency when polite reminders were ignored.
• Make shorter — a tight version under ~60 words.

docstoc also drafts SMS and WhatsApp versions of the same follow-up (SMS ≤160 characters, WhatsApp ≤280) with sms: and wa.me links that open your own messaging app. Same rule as email: docstoc writes it, you send it — nothing goes out automatically.

Chase plans & timeline

• 3-step chase plan (Solo+) — an auto-sequenced set of follow-ups with calendar dates, instead of drafting each reminder from scratch.
• Chase timeline — every reminder, reply, and payment logged per client, so you can see the full history of a chase at a glance.
• Clients & aging (Solo+) — track outstanding balances, add a contact note, and mark an invoice paid; marking paid automatically cancels any remaining planned reminders for it.
• Payment risk score (Pro+) — a 5–95 score per client, computed from their own history: how often they pay late and by how many days on average. Updates whenever you mark an invoice paid.
• Demand letter & evidence pack (Pro+) — a formal notice and an exportable record of the chase history, for escalating a stalled invoice toward collections.

Connectors

Ways to get overdue invoices into docstoc:

• CSV upload (Free) — export from QuickBooks, Xero, FreshBooks, Wave, Zoho, sevDesk, or any spreadsheet. Common column headers are mapped automatically.
• QuickBooks Online (Solo+) — native OAuth in Connector. Imports overdue invoices straight into your aging board.
• Xero (Solo+) — same OAuth flow as QuickBooks.
• Cloud storage (Solo+) — Dropbox, OneDrive, Box, or Google Drive PDF import. Google also unlocks Gmail drafts (docstoc writes into your Drafts; you send), Sheets, Calendar, and Contacts.
• Zapier / Make (Solo+) — push invoices via API key; see Webhooks & API below.

Document certificates

Free on every plan, including anonymous use with no account. Hash any file in your browser (SHA-256, via the Web Crypto API) and create a shareable, tamper-evident verification link — the file itself is never uploaded anywhere.

1. Open Certificates (or hash a file without signing in via the homepage widget).
2. Drop or choose a file — hashing happens locally; nothing leaves your browser.
3. Get a public link at docstoc.io/verify/<id> that anyone can open to check the hash — no docstoc account required on their end.
4. Revoke a certificate any time from your account; the public page immediately shows "revoked" instead of "active."

Bitcoin timestamping (OpenTimestamps)

Every certificate's hash is also submitted to the Bitcoin blockchain via OpenTimestamps, at no extra cost. This is a separate, independent proof that doesn't rely on trusting docstoc's own database:

• Submission happens in the background right after a certificate is created — it doesn't slow down issuing the certificate.
• Pending → confirmed: Bitcoin anchoring is batched, so a new certificate shows "Bitcoin timestamp pending" for a few hours before it upgrades to "Bitcoin-timestamped" once the anchor transaction is confirmed on-chain. docstoc checks for the upgrade automatically — nothing for you to do.
• Independent verification: the verify page offers a "Download the proof (.ots)" link once confirmed. That file, together with the original document, can be verified with the free ots CLI or any OpenTimestamps-compatible verifier — without needing to trust docstoc at all.

docstoc never parses or re-derives the Bitcoin proof itself; the stored .ots file is the exact bytes returned by the calendar server, re-served as-is. That's a deliberate choice — the entire point of anchoring to Bitcoin is that verification doesn't depend on any single party, docstoc included.

Audit log for chase activity

Solo+, at Audit log. Every day, docstoc hashes that day's chase events for your account — sends, opens, clicks, and replies — and chains that hash to the previous day's, forming a genuine tamper-evident ledger, not just a database column. Each day's chain hash is anchored to Bitcoin the same way document certificates are.

• Why chain the days together: altering or deleting a past day's events would break every chain hash after it, not just that one day — the same tamper-evidence property a blockchain gives a single document, applied to an ongoing activity log.
• What it's for: if a client disputes when an invoice was sent, opened, or acknowledged, the anchored chain gives you an answer that doesn't depend on anyone trusting docstoc's own records.
• Runs automatically — a new anchor is created daily for any account with chase activity; no setup required.

Trust profile & embeddable badge

Automatic once you have an active SSL domain. The moment your first domain's certificate is issued — proof of real DNS control — docstoc creates a "verified since" record for your account and anchors that claim to Bitcoin. A public page at docstoc.io/trust/<account-id> shows it, plus an embeddable badge you can put on your own site or proposals.

• What's verified: DNS control of a domain (a real, issued Let's Encrypt certificate) and, once confirmed, the date your account first reached that status. Everything else on the page — SSL status — is a live lookup, not frozen at verification time.
• What's not claimed: business registration, legal entity status, or identity. docstoc doesn't check business registries, so the trust profile never says it does.
• The badge upgrades itself from "Domain-verified via docstoc" to "Domain-verified since [date]" automatically once the Bitcoin anchor confirms.

Team & billing

Seats by plan — Free: 1 (no team), Solo: 3, Pro: 5, Enterprise: 25. An admin invites a teammate by email from Team; they accept from the emailed invite link and get the role (Admin or Member) you assigned.

Branding (Solo+, admin) — set a custom logo, workspace name, default payment link, and an optional late-fee hint line that gets inserted into drafts.

Plans — Free $0 forever, Pro $14.99/mo, Business $39.99/mo. Manage billing in Account opens Stripe's own Customer Portal for upgrades, downgrades, payment method changes, and cancellation — there's no separate in-app billing history page, Stripe's portal is the record of truth.

Webhooks & API

Outbound webhooks

Solo+ and admin-only, up to 10 endpoints per account, configured in Webhooks & API. Events: chase.drafted, chase.sent, chase.thank_you, chase.reply_drafted, chase.sequence_planned, chase.downloaded. Each delivery is a signed POST:

• X-docstoc-Event — the event name
• X-docstoc-Signature: sha256=<hmac> — HMAC-SHA256 of the body, keyed to the secret shown when you create the endpoint
• Body: { event, created_at, data }

Public API

Create an API key in Webhooks & API — the same key works for the API, Zapier, and MCP. Requires a paid plan.

Endpoint: POST https://api.docstoc.io/api/v1/chase/draft

Headers:

• Authorization: Bearer YOUR_API_KEY
• Content-Type: application/json

Body example:

{
  "client_name": "Acme Corp",
  "invoice_amount": 2400.00,
  "days_overdue": 12
}

Response is a draft subject + body, tone-matched to how overdue the invoice is — never sent on your behalf. Same shape works from Zapier's "Webhooks by Zapier" action or Make's HTTP module.

MCP

docstoc runs a public MCP (Model Context Protocol) server so Claude, ChatGPT, Grok, Perplexity, or Cursor can draft a chase directly in conversation.

Endpoint: https://api.docstoc.io/mcp

• list_templates, recommend_template, get_chase_tip — public, no signup or key needed.
• draft_chase_email — needs your docstoc API key (see above) or an active sign-in.

Rate limits: 120 requests/hour per IP overall, 30/hour specifically for draft_chase_email.

Need help?

Email founder@docstoc.io or read the FAQ on the homepage.

Open the tool