Skip to main content
CustomJS is a code-first automation platform that enables seamless integration of custom JavaScript logic into various systems and technologies, allowing users to extend applications by writing functions for tasks like sending emails, generating PDFs, or updating CRM data fields.
Use Customjs with DialNexa when a buyer, customer, partner, or account contact gives information that should change pipeline, ownership, qualification, or follow-up.

​
Where Customjs fits in a DialNexa workflow

Customjs should receive DialNexa output when the conversation affects a lead, contact, company, deal, activity, task, or account-owner alert. The handoff should explain what the caller asked for, what DialNexa learned, which record or object is affected, and who owns the next step.

Qualify callers

Capture pain, role, budget signal, timeline, objection, source, and next step before a rep follows up.

Move deals with evidence

Update stage or activity only when the caller confirms intent, decision process, urgency, or blocker.

Route hot accounts

Notify the owner when an existing account calls with expansion intent, churn risk, procurement questions, or renewal blockers.

Keep CRM hygiene clean

Search by phone, email, company, and open opportunity before creating new records.

​
What DialNexa should capture for Customjs

  • Caller name, company, email, phone, source, owner, lifecycle stage, and CRM match confidence
  • Qualification answers, pain point, objection, urgency, budget signal, and buying timeline
  • Deal stage suggestion, callback window, meeting request, task owner, and due date
  • Opt-out, wrong-number, duplicate, student, vendor, competitor, or low-fit flags
  • Recording link, transcript link, DialNexa call ID, CRM URL, calendar URL, and email thread URL

​
High-value Customjs workflows

For this scenario, DialNexa should treat Customjs as an escalation destination. Send the impact, urgency, affected customer or object, owner, and transcript link so the right team can act before the issue gets colder.
In Customjs, this should become a revenue handoff with the matched account, buying signal, stage or owner suggestion, objection, and next action. DialNexa should separate real intent from noise before creating tasks.
DialNexa should capture the preferred time, timezone, owner, promise made, and contact channel before updating Customjs. The receiving team should see exactly why the follow-up exists and what the caller expects next.
In Customjs, this should become a revenue handoff with the matched account, buying signal, stage or owner suggestion, objection, and next action. DialNexa should separate real intent from noise before creating tasks.
In Customjs, this should become a revenue handoff with the matched account, buying signal, stage or owner suggestion, objection, and next action. DialNexa should separate real intent from noise before creating tasks.
DialNexa should capture the preferred time, timezone, owner, promise made, and contact channel before updating Customjs. The receiving team should see exactly why the follow-up exists and what the caller expects next.
Use run puppeteer script when the call outcome maps clearly to that operation and the required fields, owner, review state, and evidence links are known.
Use authenticate customjs api key when the call outcome maps clearly to that operation and the required fields, owner, review state, and evidence links are known.

​
Workflows that pair Customjs with other integrations

​
Implementation notes

  • Use the DialNexa call ID as the idempotency key before running Customjs actions.
  • Write a short operational summary into Customjs 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

Match by phone, email, domain, company name, and open deal before creating or updating records. Store the DialNexa call ID on the activity.
Caller identity, company, pain, urgency, buying role, objection, requested next step, owner, and transcript link.
Log missed-call status, voicemail summary if available, retry window, owner, and whether a human callback is required.
Notify Slack for hot accounts, enterprise prospects, renewal risk, buying intent, escalation requests, or missed VIP callbacks.
No. Search contacts, companies, deals, and open tasks first. Create a new record only when the caller is new or the call changes pipeline, ownership, qualification, or follow-up.
Short and factual: who called, why they called, what DialNexa learned, what was promised, who owns the next step, and when it is due.