Skip to main content
Solar resource assessment and forecasting data for irradiance and PV power, globally.
Use Solcast with DialNexa when spoken context should become structured data that teams can query, enrich, report on, or review.

​
Where Solcast fits in a DialNexa workflow

Solcast should receive DialNexa output when the conversation affects a row, dataset, lookup result, enrichment record, dashboard event, warehouse record, or review queue. The handoff should explain what the caller asked for, what DialNexa learned, which record or object is affected, and who owns the next step.

Join call context

Match phone or email to CRM, product, billing, support, account, or external IDs before syncing.

Build review queues

Route low-confidence matches, missing data, suspicious lookups, and edge cases for review.

Power reporting

Track call reasons, qualified outcomes, missed-call impact, churn risk, and conversion quality.

Normalize call outcomes

Store intent, category, urgency, product, owner, and next action in fields reporting can trust.

​
What DialNexa should capture for Solcast

  • Caller ID, contact ID, account ID, source system, external ID, and match confidence
  • Structured outcome, intent, category, sentiment, urgency, product, region, and owner
  • Lookup result, enrichment value, qualification fields, revenue signal, support reason, and next action
  • Timestamp, duration, transcript URL, recording URL, DialNexa call ID, and raw payload reference
  • Data quality fields such as duplicate status, missing fields, confidence, and review needed

​
High-value Solcast workflows

For this scenario, DialNexa should send structured fields into Solcast: matched identity, lookup result, confidence, timestamp, and the decision that depends on it. Keep full transcripts linked, not copied.
For this workflow, DialNexa should send Solcast a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
DialNexa should send Solcast the source, consent state, call outcome, audience impact, and suppression or enrollment decision. The goal is better targeting, not another generic campaign touch.
For this workflow, DialNexa should send Solcast a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
For this scenario, DialNexa should send structured fields into Solcast: matched identity, lookup result, confidence, timestamp, and the decision that depends on it. Keep full transcripts linked, not copied.
For this scenario, DialNexa should send structured fields into Solcast: matched identity, lookup result, confidence, timestamp, and the decision that depends on it. Keep full transcripts linked, not copied.
For this scenario, DialNexa should send structured fields into Solcast: matched identity, lookup result, confidence, timestamp, and the decision that depends on it. Keep full transcripts linked, not copied.
For this scenario, DialNexa should send structured fields into Solcast: matched identity, lookup result, confidence, timestamp, and the decision that depends on it. Keep full transcripts linked, not copied.
Use create pv power resource only when DialNexa has a matched caller, a clear destination object, and enough call context to justify opening a new data record. If the caller is unclear, route to review instead of creating noise.
Use update pv power resource when the caller changes a field, status, owner, date, priority, note, consent choice, or next step on an existing Solcast record. Include the old value, new value, and reason from the call.

​
Workflows that pair Solcast with other integrations

​
Implementation notes

  • Use the DialNexa call ID as the idempotency key before running Solcast actions.
  • Write a short operational summary into Solcast 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, if the lookup is fast and confidence is visible. Use fallback routing when enrichment fails.
Include lookup timestamp, source, confidence, and expiration rules.
Conversion labels, spam suppression, duplicate matching, missing owners, and high-impact categories.
Reject or review records with missing identity, conflicting external IDs, impossible values, or sensitive data in the wrong destination.
Version fields, document meanings, and test downstream dashboards before changing production payloads.
Usually no. Store structured fields, summaries, and links to restricted transcripts.
Intent, category, source, owner, outcome, urgency, customer ID, timestamp, and DialNexa call ID.
Send them to a review queue with match reason, confidence, candidate records, and transcript link.