Skip to main content
Botpress is an open-source platform for building, deploying, and managing chatbots.
Use Botpress with DialNexa when the call depends on a file, form, PDF, signature, contract, storage folder, or document review.

​
Where Botpress fits in a DialNexa workflow

Botpress should receive DialNexa output when the conversation affects a file, document, folder, form submission, PDF, extracted field, signature request, or review task. The handoff should explain what the caller asked for, what DialNexa learned, which record or object is affected, and who owns the next step.

Prepare document handoffs

Capture document type, owner, missing fields, requested change, deadline, and approval path.

Extract or verify fields

Compare caller statements with parsed invoice, ID, contract, form, or PDF data before approval.

Route signature blockers

Record who needs to sign, what term is disputed, what changed, and whether legal or finance must review.

Store evidence correctly

Keep recordings, transcripts, generated PDFs, and signed documents beside the customer or case record.

​
What DialNexa should capture for Botpress

  • Caller, account, document type, file link, folder path, submission ID, signer, and permission level
  • Requested change, extracted fields, missing fields, signer details, deadline, and approval owner
  • Exception reason, document version, customer expectation, and promised next step
  • Transcript link, recording link, DialNexa call ID, CRM link, ticket link, and storage folder link
  • Redaction, retention, access, and sensitive-document flags

​
High-value Botpress workflows

DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in Botpress. Sensitive files should stay behind restricted links.
DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in Botpress. Sensitive files should stay behind restricted links.
DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in Botpress. Sensitive files should stay behind restricted links.
For this workflow, DialNexa should send Botpress a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in Botpress. Sensitive files should stay behind restricted links.
Use update account when the caller changes a field, status, owner, date, priority, note, consent choice, or next step on an existing Botpress record. Include the old value, new value, and reason from the call.
Treat delete file as a controlled workflow. DialNexa should capture the caller’s reason, identity confidence, approval owner, and rollback path before anything destructive or irreversible happens in Botpress.

​
Workflows that pair Botpress with other integrations

​
Implementation notes

  • Use the DialNexa call ID as the idempotency key before running Botpress actions.
  • Write a short operational summary into Botpress and link to the full transcript or recording for audit.
  • Map required fields before launch: destination object, owner, status, urgency, next step, and record URL.
  • Create review paths for low-confidence matches, sensitive requests, high-value customers, and actions that change money, access, legal terms, or customer commitments.

​
FAQs

Yes for approved templates such as confirmations, quotes, or summaries. Use review for legal, billing, or high-value documents.
IDs, contracts, tax documents, payment images, private health or HR files, and full recordings.
Verify recipient, document type, and permission before sending. Log what was sent and why.
The document link, caller explanation, missing or disputed fields, requested outcome, owner, and transcript link.
No. Store links, extracted fields, and why the document matters. Keep sensitive files in controlled storage.
Missing fields, low-confidence extraction, signature blockers, legal language, identity files, and money-related changes should go to review.