Budget Tracker

Identifying Mentions of Budget and Discounts

The “Budget” tracker detects references to financial constraints, pricing concerns, discounts, or budget-related conditions. Understanding these mentions helps teams assess pricing discussions, identify cost-related objections, and inform strategic decisions on pricing models, promotions, and resource allocation.

Who Benefits:

  • Project Managers & Team Leads: Recognize when budget issues surface, guiding training to handle cost-related queries effectively.
  • Sales & CX Teams: Identify how often customers inquire about discounts or mention budget limitations, informing tailored offerings or concessions.
  • Business Managers & Strategists: Spot trends in budget considerations and refine pricing strategies, promotional campaigns, or product positioning.
  • Compliance Officers: Confirm that representatives mention only approved pricing options and adhere to guidelines on discussing budgets or discounts.

Value Proposition:

  • Market & Customer Insight: Highlighting budget mentions reveals how pricing sensitivities affect sales and retention.
  • Operational Efficiency: Machine-readable JSON output integrates into dashboards, supporting data-driven pricing and promotional decisions.
  • Continuous Improvement: Tracking discussions about budget and discounts informs continuous refinement of sales tactics and product value propositions.

Data Dictionary

Objective:

Detect phrases in the conversation that indicate budget considerations or requests about discounts. The tracker returns occurrences of matched phrases, along with timestamps and confidence. This data helps teams understand the frequency and context of financial discussions.

Proposed JSON Schema:

{
  "trackers": [
    {
      "name": "Budget",
      "matches": [
        {
          "text": "<string>",
          "timestamp": "<ISO 8601 or relative time>",
          "confidence": <number> // 0.0 to 1.0
        }
      ]
    }
  ]
}

Data Dictionary:

FieldDescriptionExample
trackersArray of tracker objects.[ {...} ]
trackers[].nameThe tracker’s name."Budget"
trackers[].matchesArray of matches for phrases indicating budget or discount mentions.[ {...}, {...} ]
matches[].textThe matched phrase representing a budget or discount-related mention."Do you have any discounts on this package?"
matches[].timestampWhen the phrase occurred (ISO 8601 or relative time)."2024-07-10T11:10:00Z" or "00:03:50"
matches[].confidenceConfidence (0.0 to 1.0) indicating how closely the phrase aligns with budget/discount intent.0.85

If No Matches Found:
If no budget-related mentions are detected, return an empty matches array for "Budget" or omit the tracker. If no trackers match at all, return:

{
  "trackers": []
}

Determining Confidence & Thresholds

How the Budget Tracker Works:

  • Seed the tracker with phrases associated with budgets, costs, or discounts (e.g., "budget constraints," "any discount available," "lower the price," "on a tight budget").
  • The system interprets these seed phrases and identifies semantically related statements.
  • Confidence indicates how closely the detected phrase aligns with discussing budgets or discounts.

Confidence & Calibration:

  • Initial Testing: Validate on known calls to confirm that detected phrases accurately represent budget or discount discussions.
  • Refine Phrases: Add or remove seed phrases to capture evolving pricing conversations.
  • Thresholding: Downstream processes can filter low-confidence matches if necessary.
  • Stakeholder Feedback: Include insights from sales leads or compliance officers to refine which budget mentions matter most.

Prompt Construction & Instructions

Role Specification & Reiteration:

  • Present the system as a “highly experienced assistant” identifying budget or discount mentions.
  • Reiterate instructions: return only JSON, follow schema, no extra commentary.

No Hallucination:

  • Only detect budget-related phrases if supported by transcript evidence.
  • If uncertain, assign a lower confidence or omit matches.

Strict Formatting:

  • Return only JSON with trackers.
  • If none found, return empty trackers.

Example Prompt for Implementation

System Message (Role: System):
"You are a highly experienced assistant that identifies 'Budget' mentions in a conversation. You have:

  • A transcript
  • A 'Budget' tracker defined by seed phrases indicating budget or discount concerns.

Your task:

  1. Detect phrases where the customer talks about budget constraints, requests discounts, or indicates price sensitivity.
  2. Return text, timestamp, and confidence.
  3. Return only JSON as defined. No extra commentary.

Instructions & Variables (example):

{
  "tracker": {
    "name": "Budget",
    "phrases": [
      "Do you offer discounts",
      "within my budget",
      "reduce the price",
      "any coupon code"
    ]
  }
}

User Message (Role: User):
"Analyze the following transcript and detect 'Budget' mentions:

[TRANSCRIPT_JSON][TRANSCRIPT_JSON]"

Expected Output Format:

{
  "trackers": [
    {
      "name": "Budget",
      "matches": [
        {
          "text": "Is there any discount if I buy in bulk?",
          "timestamp": "2024-07-10T11:10:00Z",
          "confidence": 0.9
        }
      ]
    }
  ]
}