Skip to main content
TradeVulcan logoTradeVulcan
Work Mode Guides
Vulcan Intelligence

Use Work Mode alongside CallSpark and Vulcan Voice

Find available call context, prepare operational follow-up and keep phone routing, voice-agent settings and live calling in their owning apps.

Begin with the call question

Vulcan Intelligence’s workspace context can include authorized call and message records relevant to a specific question. Ask about a named customer or identifiable call, and inspect the record links and coverage in the answer. The available summary is not automatically a full transcript or recording.

The documented Work capability catalog does not provide dedicated controls to buy numbers, change CallSpark routing, place arbitrary calls or rewrite a Vulcan Voice agent. Those operations belong in their owning applications and setup flows.

A practical missed-inquiry workflow

  1. Locate the relevant call or customer record and verify the date and source.
  2. Ask for a summary of the information actually available. Do not have Work fill missing transcript detail with plausible dialogue.
  3. Decide whether the next step is an internal note, one-to-one reply or review in the call workspace.
  4. Prepare that supported action separately and check its exact target before approval.

Try a focused prompt

TRY THIS PROMPT

Find the available call and message context for the selected customer’s recent generator inquiry. Summarize only the records you can read, identify missing details, and propose a callback checklist. Do not place a call, change routing or promise an appointment.

If Work cannot access the required source, open CallSpark or Vulcan Voice directly. You can supply an appropriate non-sensitive export or summary for analysis; make clear that it is supplied material, not a fresh live read.

Prepare changes for the owning app

For a routing or voice-agent improvement, ask for a review checklist: desired destinations, business hours, escalation rules, approved greeting and how to test. Apply the actual settings through the app’s supported controls, then verify the result with the correct test procedure.

A written script is not an installed voice configuration. A recommended callback is not a completed call. A successful internal note is not a customer notification. Keep those outcomes separate in the conversation.

When reporting call performance

Specify the source and period. Search results are bounded records, not a complete calls dashboard. Use an available report or the app’s reporting screen for totals, and preserve its definitions for answered, missed, qualified and booked. Do not combine those statuses as if they measured the same thing.

Continue learning