3.1 Overview

The Dashboard is the main operational summary for an AIUNIFY Assistant account. It provides a high-level view of calling activity, Lead engagement, AI Agents, Campaigns, recent Call Logs, and total conversation time.

The Dashboard is intended to answer questions such as:

The Dashboard retrieves authenticated account statistics from:

The returned information includes four summary metrics, a seven-day call chart, five recent Call Log records, and separate counts for Leads, contacted Leads, uncontacted Leads, AI Agents, and Campaigns.

Opening the Dashboard

3.2 Accessing the Dashboard

After signing in:

1. Locate Dashboard in the Sidebar.
2. Select it once.
3. Wait for the loading indicator to disappear.
4. Confirm that the page heading displays Dashboard.
5. Review the summary cards before opening another section.

The Dashboard requires a valid authentication token. The frontend sends that token with the statistics request and displays an error when the request cannot be completed.

3.3 Dashboard Loading Indicator

While statistics are being retrieved, AIUNIFY Assistant displays a rotating loading symbol.

During this period:

1. Do not repeatedly select Dashboard.
2. Do not create another browser tab unnecessarily.
3. Allow the first request to complete.
4. Confirm that the internet connection remains available.
5. Wait before refreshing the page.

When the request succeeds, the Dashboard cards and activity panels appear.

3.4 Dashboard Sections

The Dashboard contains five primary areas:

Each area summarizes information stored elsewhere in the system. The Dashboard does not replace the detailed Leads, Campaigns, Call Logs, AI Agents, Phone Numbers, or Settings pages.

Dashboard Data Scope

3.5 What a Normal User Sees

For a normal account, the Dashboard generally counts records owned by the signed-in user.

The statistics route filters:

This means a normal user’s Dashboard is primarily an account-specific view rather than a platform-wide report.

3.6 Super Administrator View

A Super Administrator can receive global totals instead of totals restricted to one user.

A global Dashboard can therefore include:

A Super Administrator should not compare global totals directly with the totals shown to a normal user.

3.7 Owned Resources Versus Shared Resources

The inspected Dashboard calculates normal-user Lead, Campaign, and AI Agent counts using the record’s ownership field.

A user who can access resources shared by an administrator may not always see those shared resources reflected in the same way as resources the user personally owns.

Therefore:

When a total appears lower than expected, review whether the missing record is owned by the user or merely shared with the user.

Dashboard Summary Cards

3.8 Summary Cards

The top of the Dashboard displays four cards:

These values are produced from the account’s Lead and Call Log records.

Total Calls

3.9 Meaning of Total Calls

Total Calls represents the number of Call Log records included in the Dashboard calculation.

The metric is labeled:

The system counts all Call Logs available within the user’s Dashboard scope.

This can include calls with statuses such as:

Total Calls should not be interpreted as the number of successful conversations.

3.10 What Total Calls Includes

The calculation is:

Example:

The Dashboard would display:

3.11 Total Calls Versus Unique Leads

A single Lead can have more than one Call Log.

Example:

This activity represents:

Do not expect Total Calls to equal Total Leads.

3.12 Total Calls Versus Campaign Leads

A Campaign can contain 100 Leads without creating 100 Call Logs immediately.

Call Logs are produced as calling activity occurs.

Therefore:

Possible reasons include:

1. The Campaign has not started.
2. The Campaign is scheduled for later.
3. Only part of the Lead list has been processed.
4. Calling was stopped.
5. A provider problem prevented calls from initiating.
6. Some Leads were removed before being called.

Success Rate

3.13 Meaning of Success Rate

The Dashboard defines Success Rate as the percentage of Call Logs whose status equals:

The calculation is:

The resulting percentage is rounded to the nearest whole number.

3.14 Success-Rate Example

Assume the Dashboard contains:

Calculation:

The Dashboard displays:

3.15 What “Completed” Means

A completed Call Log means the calling process reached the system’s completed status.

It does not automatically mean:

1. The Lead purchased a product.
2. The Lead was qualified.
3. An Appointment was booked.
4. The person was interested.
5. The Agent achieved the Campaign objective.
6. The customer was satisfied.
7. A follow-up is unnecessary.

The detailed Call Log, transcript, analysis, and Lead qualification information must be reviewed before determining the business outcome.

3.16 Completed Call Versus Successful Business Outcome

Consider this example:

The call contributes to the Dashboard’s Success Rate because its technical status is completed.

However, it may not represent a successful sales result.

For this reason, the Dashboard’s Success Rate is best understood as:

rather than:

3.17 Why Success Rate Can Be Low

A lower Success Rate can result from:

Open Call Logs and filter by status to identify the actual reason.

3.18 Why Success Rate Can Change

The Success Rate can change as Call Log statuses change.

Example:

A Campaign that is still running may therefore show an incomplete or temporarily low percentage.

3.19 Zero Success Rate

A Success Rate of 0% can mean:

1. No calls exist.
2. Calls exist but none are completed.
3. All calls failed.
4. All calls are still pending or active.
5. Provider callbacks have not updated the logs.
6. The Dashboard has not been refreshed.

Do not assume the telephony system is broken based only on a zero percentage.

Total Leads

3.20 Meaning of Total Leads

Total Leads represents the number of Lead records included in the signed-in user’s Dashboard scope.

The card also displays the number identified as contacted.

Example:

The Dashboard obtains the total by counting Lead records rather than counting telephone numbers inside Campaigns.

3.21 What Counts as a Lead

A Lead is counted when a Lead record exists in the system.

The record does not need to be:

1. Assigned to a Campaign.
2. Successfully called.
3. Qualified.
4. Connected to an Appointment.
5. Associated with a completed call.

Recently imported Leads can therefore increase Total Leads immediately, even before calling begins.

3.22 Duplicate Lead Records

When the same person exists in two separate Lead records, both records can be included in Total Leads.

Example:

The Dashboard may count:

Duplicate cleanup should be performed in the Leads section rather than assumed from the Dashboard total.

Contacted Leads

3.23 Meaning of Contacted Leads

The Dashboard determines contacted Leads by identifying distinct Lead IDs that appear in Call Logs.

The calculation does not filter those Call Logs to completed status.

Therefore, a Lead can be counted as contacted when the related call was:

In practical terms, the Dashboard’s contacted count means:

It does not necessarily mean:

This distinction is important when evaluating outreach performance.

3.24 Contacted-Lead Example

Assume these records exist:

The Dashboard calculation can show:

Only Lead A had a completed call, but Leads A, B, and C have Call Log activity.

3.25 Repeated Calls Do Not Repeatedly Increase Contacted Leads

The Dashboard uses distinct Lead IDs.

Example:

The Lead contributes:

This prevents repeated call attempts from inflating the contacted-Lead count.

3.26 Contacted Does Not Mean Qualified

A contacted Lead may still be:

Use the Call Log analysis and Lead record for the actual disposition.

Uncontacted Leads

3.27 Meaning of Uncontacted Leads

The Dashboard calculates:

The application prevents the displayed number from dropping below zero.

An uncontacted Lead generally has no Lead-linked Call Log inside the Dashboard scope.

3.28 Why Leads Remain Uncontacted

Possible reasons include:

1. The Lead was recently created.
2. The Lead has not been assigned to a Campaign.
3. The Campaign is scheduled for later.
4. The Campaign has not reached that Lead.
5. The Campaign was stopped.
6. The Lead was excluded by filtering or selection.
7. Calling resources were not configured.
8. The Lead has an invalid or missing number.
9. The account reached a Plan limit.
10. The Lead belongs to another user.

3.29 Using Uncontacted Leads as a Work Queue

The uncontacted count can help identify potential remaining outreach work.

Before creating another Campaign, confirm:

Do not automatically place every uncontacted Lead into a new Campaign.

Talk Time

3.30 Meaning of Talk Time

Talk Time represents the sum of the duration values stored in Call Logs.

The backend adds the durations in seconds and converts the result into whole minutes:

The displayed value is rounded down to the nearest whole minute.

3.31 Talk-Time Example

Assume these Call Logs contain:

Total:

Conversion:

The Dashboard displays:

3.32 Partial Minutes

The system rounds down because it uses whole-minute conversion.

Example:

Example:

This means the Dashboard Talk Time is a summarized operational value rather than a precise billing total.

3.33 Talk Time Is Not Provider Billing

The Dashboard Talk Time should not automatically be used to calculate provider charges.

Provider billing may consider:

Review the appropriate telephony and AI provider statements for financial reconciliation.

3.34 Talk Time Shows Zero

Talk Time can display 0m when:

1. No calls exist.
2. Calls have no stored duration.
3. All calls ended before one full combined minute.
4. Provider callbacks have not supplied duration.
5. Calls are still active.
6. Call reconciliation has not completed.
7. Logs were imported without duration values.

Open Call Logs to inspect individual durations.

Seven-Day Call-Volume Chart

3.35 Overview Chart

The Dashboard contains a chart titled:

Its description states:

The chart displays one bar for each day and uses the Call Log creation date to count daily activity.

3.36 Date Range

The chart includes:

The labels use abbreviated weekday names such as:

This is a rolling seven-day view, not necessarily a Sunday-through-Saturday calendar week.

3.37 What the Bars Represent

Each bar represents the number of Call Logs created during that calendar day.

The chart does not show only completed calls.

A day’s call volume can include:

Move the pointer over a bar to see the number of calls for that day.

3.38 Chart Example

Suppose the last seven days contain:

The chart displays seven bars reflecting those totals.

A taller bar means more Call Logs were created on that day. It does not necessarily indicate better Campaign performance.

3.39 High Call Volume

A high-volume day can result from:

1. A large Campaign.
2. Multiple Campaigns.
3. Repeated attempts.
4. Inbound and outbound activity.
5. A retry process.
6. A high number of failed or no-answer calls.
7. Increased customer demand.

Review the Call Logs before interpreting high volume as success.

3.40 Low Call Volume

A low-volume day can result from:

1. No Campaign scheduled.
2. A Campaign being stopped.
3. Fewer Leads.
4. Plan or usage limits.
5. Provider configuration problems.
6. An inactive calling number.
7. A holiday or intentionally restricted calling period.
8. A Campaign scheduled in another time zone.

3.41 Empty Chart

An empty or zero-value chart can be normal when:

1. The account is new.
2. No calls occurred during the past seven days.
3. Older lifetime calls exist outside the chart period.
4. Call Logs were deleted.
5. The Dashboard failed to retrieve data.

Total Calls can be greater than zero while the seven-day chart remains empty because Total Calls is lifetime-based and the chart covers only seven days.

Recent Activity

3.42 Recent Activity Panel

The Dashboard displays a Recent Activity panel described as:

It retrieves the five newest Call Logs and includes available Lead and AI Agent names.

3.43 Information Shown for Each Activity

A recent activity entry can show:

The time is formatted using the account’s selected time-display preference.

3.44 Lead Initial

The circular icon beside an activity uses the first character of the Lead’s name.

Example:

When no Lead name is available, the interface can display:

and identify the item as a system event.

3.45 AI Agent Name

Below the Lead name, the entry can display:

Example:

When the Agent record is unavailable or not populated, the name may be blank.

3.46 Inbound Indicator

An inbound activity can display a small blue indicator beside the Lead name.

The indicator helps distinguish an inbound interaction from an outbound Campaign call.

The absence of the blue indicator generally means the entry is not marked as inbound.

Recent Activity Statuses

3.47 Pending Execution

Internal status:

Dashboard label:

The call is recorded but has not progressed into an active calling stage.

3.48 Queued

Internal status:

Dashboard label:

The call is waiting to be processed.

A queued status can remain temporarily while:

1. Earlier calls are being handled.
2. Campaign concurrency limits are active.
3. The provider has not yet begun the call.
4. The Campaign scheduler is processing records.

3.49 Initiating

Internal status:

Dashboard label:

The system has begun the calling process but the destination is not yet shown as ringing.

3.50 Ringing

Internal status:

Dashboard label:

The destination telephone is being alerted.

Ringing does not mean the call has been answered.

3.51 In Conversation

Internal status:

Dashboard label:

The call is currently active according to the provider status.

Do not edit or delete an associated running Campaign merely because the Dashboard is still updating.

3.52 Contact Successful

Internal status:

Dashboard label:

This label means the Call Log reached completed status.

As explained earlier, the user must still inspect the transcript and outcome before treating the call as a successful sale, qualification, or Appointment.

3.53 Call Failed

Internal status:

Dashboard label:

Possible causes can include:

1. Invalid telephone number.
2. Provider rejection.
3. Authentication problem.
4. Network failure.
5. Carrier issue.
6. Number configuration problem.
7. Call-routing failure.

Open the full Call Log for additional details.

3.54 Line Busy

Internal status:

Dashboard label:

The destination could not accept the call because the line was engaged or the provider returned a busy response.

A retry may be appropriate according to the organization’s Campaign policy.

3.55 No Answer

Internal status:

Dashboard label:

The call did not receive an answered connection.

This Lead can still be counted as contacted on the Dashboard because a Call Log exists.

3.56 Canceled

Internal status:

Dashboard label:

The call was canceled before completing.

Possible reasons include:

1. Campaign stopped.
2. Provider canceled the attempt.
3. User action.
4. Scheduling change.
5. System interruption.

3.57 Unknown Status

When the Dashboard receives a status it does not recognize, it falls back to the pending configuration.

A newly introduced backend status may therefore temporarily appear as Pending Execution until the frontend status mapping is updated.

3.58 Activity Time

The Recent Activity time is displayed according to the account’s selected time format.

The system’s Settings provider controls whether time is presented in the configured display style.

When the time seems incorrect, review:

3.59 Viewing All Logs

At the bottom of Recent Activity, select:

This opens:

Use the full Call Logs section to review:

1. Direction
2. Status
3. Duration
4. Recording
5. Transcript
6. Summary
7. Lead qualification
8. Campaign
9. Agent
10. Provider details

The Dashboard shows only the five newest activity records.

3.60 Empty Recent Activity Panel

The Recent Activity panel can appear empty when:

1. The account has no Call Logs.
2. Logs belong to another user.
3. The account is new.
4. Records were removed.
5. The statistics request returned no recent activity.

The inspected interface does not display a separate “No recent activity” message inside the list. An empty panel can therefore be normal.

Resource Count Cards

3.61 Resource Cards

Below the chart and Recent Activity panel are three additional cards:

These provide direct navigation to the operational sections.

3.62 Leads Resource Card

The Leads card displays:

It contains a link labeled:

Selecting it opens:

Although the interface uses the phrase Manage Workforce, the destination is the Leads management page.

3.63 Contacted and Uncontacted Indicators

The Leads card uses separate visual indicators:

These colors help compare the two groups quickly.

The status is still based on Call Log association, not confirmed conversation success.

3.64 AI Agents Resource Card

The AI Agents card displays the number of owned AI Agent records.

It includes the link:

Selecting it opens:

Use the Agents section to create, test, edit, or review the Agents represented by the count.

3.65 Agent Count Does Not Mean Ready Agents

The Agent count includes created Agent records.

An Agent can be counted even when it still requires:

Do not launch a Campaign solely because the Agent count is greater than zero.

3.66 Campaigns Resource Card

The Campaigns card displays the number of Campaign records owned by the account.

It includes the link:

Selecting it opens:

The count can include Campaigns in multiple operational states.

3.67 Campaign Count Does Not Mean Active Campaigns

The Campaign total can include:

Open the Campaigns section to determine the actual status of each Campaign.

New Campaign Button

3.68 Opening Campaign Creation

The top-right area of the Dashboard contains:

Selecting it directs the user to the Campaigns page.

From there, the user can begin the Campaign-creation process.

The Dashboard button does not itself prove that all required resources are configured.

3.69 Before Selecting New Campaign

Confirm that:

1. An active Plan or applicable trial is available.
2. At least one Lead exists.
3. At least one AI Agent exists.
4. The intended Agent has been tested.
5. A calling resource is configured.
6. Provider credentials are valid.
7. Campaign limits have not been reached.
8. Calling times are appropriate.
9. Consent and compliance requirements are satisfied.

Dashboard Refresh Behavior

3.70 When Dashboard Data Loads

The inspected frontend requests Dashboard data when the Dashboard page loads.

The page does not show a dedicated manual Refresh button.

The inspected version also does not show a repeating Dashboard polling timer. Therefore, the visible totals may remain unchanged until the page is reloaded or reopened.

3.71 Refreshing Dashboard Metrics

To retrieve updated totals:

1. Allow active calls to finish.
2. Wait briefly for provider status updates.
3. Refresh the browser once.
4. Reopen Dashboard from the Sidebar when necessary.
5. Confirm that the loading symbol appears.
6. Review the updated totals.

Do not repeatedly refresh during an active Campaign, because provider status updates may still be processing.

3.72 Real-Time Call Status Versus Dashboard Snapshot

Certain calling systems can send real-time events, but the Dashboard statistics page examined here operates primarily as a fetched summary.

Treat it as:

rather than:

Use Campaign Details and Call Logs when close monitoring is required.

Operational Readiness

3.73 Dashboard Readiness Versus System Readiness

The Dashboard shows activity and resource counts, but it does not display every condition required for a successful call.

A Dashboard can show:

while the account is still unable to place calls because:

1. No Phone Number is configured.
2. No active SIP Trunk exists.
3. Twilio credentials are missing.
4. The Plan is inactive.
5. Usage limits were reached.
6. The Agent was not properly configured.
7. The Lead numbers are invalid.
8. The Campaign is scheduled for later.

3.74 Account Readiness

Confirm:

The platform tracks current Plan usage for Agents, Campaigns, Leads, and monthly Calls. Trial accounts use configured trial limits, while paid accounts use their Plan limits.

3.75 Telephony Readiness

Confirm one supported calling method is available:

Also confirm:

1. Provider credentials are valid.
2. The number supports the intended direction.
3. Caller ID is approved.
4. Inbound routing is correct.
5. Outbound calls are permitted.
6. The provider account has sufficient capacity.

3.76 AI Agent Readiness

Confirm the selected Agent has:

An Agent should be tested independently before being used with a large Lead list.

3.77 Lead Readiness

Confirm the selected Leads have:

A high Lead count on the Dashboard does not establish Lead quality.

3.78 Campaign Readiness

A Campaign requires:

The Campaign creation interface requires at least one selected Lead and an Agent. The backend also validates ownership of the Agent and Leads before allowing Campaign changes.

3.79 Compliance Readiness

Before launching outbound activity, review:

The Dashboard does not verify all legal conditions on the business’s behalf.

3.80 Appointment Readiness

When the Agent can book Appointments, confirm:

1. Availability has been configured.
2. Appointment duration is correct.
3. Time zone is correct.
4. Available dates and hours are accurate.
5. The Agent has the correct booking tool.
6. Notification settings are active.
7. A test booking has been completed.

3.81 Knowledge Readiness

Before production calls:

1. Review the Knowledge Base.
2. Remove outdated pricing.
3. Remove conflicting policies.
4. Confirm business hours.
5. Confirm service descriptions.
6. Confirm Appointment policies.
7. Test common questions.
8. Confirm the Agent does not invent unsupported answers.

Reading Dashboard Patterns

3.82 Many Leads, Few Calls

Example:

Possible interpretation:

1. Most Leads have not been placed into a Campaign.
2. A Campaign is newly started.
3. Calling is intentionally limited.
4. The Campaign was stopped early.
5. The account reached a usage limit.

Review Campaigns and uncontacted Leads.

3.83 Many Calls, Few Contacted Leads

Example:

Possible interpretation:

1. Leads were called repeatedly.
2. Retry activity is high.
3. Many Leads required several attempts.
4. Campaigns reused the same Lead list.

Review duplicate Campaign assignments and repeated call policies.

3.84 High Completion Rate, Low Business Results

Example:

Possible interpretation:

1. Calls are connecting technically.
2. The Agent’s script may need improvement.
3. Lead targeting may be weak.
4. The offer may not match the audience.
5. The Knowledge Base may be insufficient.
6. The qualification or booking tool may not be configured.

Review transcripts and Lead outcomes.

3.85 Low Completion Rate, Strong Connected Results

Example:

Possible interpretation:

1. Lead quality is strong when people answer.
2. Telephone reachability is weak.
3. Call times may be inappropriate.
4. Number formatting may be inconsistent.
5. More attempts may be needed within approved policy.

3.86 High Talk Time, Low Call Count

Example:

Possible interpretation:

1. Conversations are long.
2. The Agent is handling complex inquiries.
3. Calls may not be ending efficiently.
4. The prompt may need shorter responses.
5. Appointment or transfer conversations may be extended.

Review recordings and transcripts.

3.87 High Call Count, Low Talk Time

Example:

Possible interpretation:

1. Many calls were not answered.
2. Calls failed quickly.
3. Lines were busy.
4. Invalid numbers exist.
5. Calls were canceled.
6. Conversations ended immediately.

Filter Call Logs by status.

Daily Dashboard Workflow

3.88 Beginning-of-Day Review

At the beginning of the operating day:

1. Open Dashboard.
2. Record Total Calls where internal reporting requires it.
3. Review Success Rate.
4. Review the seven-day trend.
5. Review Recent Activity.
6. Check for failed, busy, or no-answer patterns.
7. Review uncontacted Leads.
8. Open Campaigns.
9. Confirm scheduled Campaigns.
10. Confirm provider and Plan readiness.

3.89 During-Campaign Review

While a Campaign is running:

1. Review Campaign Details.
2. Use Dashboard as a summary.
3. Refresh only when necessary.
4. Watch Recent Activity statuses.
5. Open Call Logs for failures.
6. Confirm calls are progressing beyond queued or ringing.
7. Stop the Campaign when a serious configuration problem appears.
8. Correct the problem before restarting.

3.90 End-of-Day Review

At the end of calling activity:

1. Refresh Dashboard.
2. Review Total Calls.
3. Review completed-call percentage.
4. Review Talk Time.
5. Compare contacted and uncontacted Leads.
6. Review the latest five activities.
7. Open Call Logs for the full day.
8. Review failed and no-answer records.
9. Review transcripts and qualification.
10. Confirm Appointments.
11. Document corrective actions for the next Campaign.

Troubleshooting the Dashboard

3.91 “Failed to Load Dashboard Metrics”

When the Dashboard request fails, the interface displays:

This can result from:

1. Expired authentication.
2. Invalid authentication token.
3. Backend API outage.
4. Network interruption.
5. Incorrect API configuration.
6. Server error.
7. Browser extension interference.

The error message is generated when the authenticated Dashboard statistics request fails.

3.92 Correcting a Dashboard Load Failure

Try:

1. Wait several seconds.
2. Refresh once.
3. Open another protected page.
4. Confirm that the login session is active.
5. Sign out and sign back in.
6. Try a private browser window.
7. Disable an interfering browser extension.
8. Confirm the API is operating.
9. Report the time of the error to Support.

Do not create duplicate Leads or Campaigns because the Dashboard temporarily failed.

3.93 Dashboard Remains Blank

When the loading symbol disappears but no Dashboard appears:

1. Confirm the browser console is not required for normal use.
2. Refresh once.
3. Confirm the statistics response completed.
4. Sign out and back in.
5. Clear outdated site data when authorized.
6. Try another browser.
7. Contact Support.

The inspected frontend returns no Dashboard content when the data object remains unavailable after loading.

3.94 Totals Appear Stale

Possible reasons include:

1. Dashboard was loaded before recent calls finished.
2. The page does not continuously poll for updates.
3. Provider callbacks are delayed.
4. Call reconciliation is still processing.
5. Another user owns the records.
6. Shared resources are not included in ownership totals.

Refresh the Dashboard after the activity has settled.

3.95 Total Calls Does Not Match Campaign Details

Possible reasons include:

Use filtered Call Logs for reconciliation.

3.96 Contacted Leads Appear Too High

Remember that the Dashboard marks a Lead contacted when its ID appears in any Call Log.

Failed, busy, and no-answer calls can therefore contribute to the contacted count.

3.97 Contacted Leads Appear Too Low

Check whether:

1. The Call Log is linked to the correct Lead.
2. The call was recorded as a system event without a Lead.
3. The Lead belongs to another user.
4. The activity occurred before the Lead record was connected.
5. The Dashboard needs refreshing.
6. The Lead is shared rather than owned.

3.98 Talk Time Appears Lower Than Expected

Possible reasons include:

1. Durations are rounded down to whole minutes.
2. Some Call Logs have no duration.
3. Active calls have not ended.
4. Provider updates are delayed.
5. Ringing time is not counted as conversation duration.
6. Calls belong to another account.

3.99 Success Rate Appears Too High

The rate counts completed Call Logs, not sales success.

Review transcripts and outcomes before using the metric in business-performance reporting.

3.100 Success Rate Appears Too Low

Check for:

1. Pending calls.
2. Queued calls.
3. Running calls.
4. No-answer calls.
5. Failed calls.
6. Busy lines.
7. Provider callback delays.
8. Incorrect telephone formatting.
9. Campaigns that were stopped.

3.101 Recent Activity Does Not Show a Call

The Recent Activity panel displays only five records.

Select View all logs to locate older activity.

Also confirm:

1. The Call Log belongs to the signed-in user.
2. The call was saved.
3. The Dashboard was refreshed.
4. The provider callback completed.

3.102 Incorrect Activity Time

Review:

1. Account time zone.
2. Selected 12-hour or 24-hour format.
3. Device time.
4. Browser time.
5. Server-stored Call Log date.
6. Whether daylight-saving time applies.

3.103 Dashboard Shows Zero Agents

Open AI Agents and confirm:

1. An Agent exists.
2. The Agent belongs to the signed-in user.
3. The Agent was successfully saved.
4. The Agent was not deleted.
5. The Dashboard was refreshed.

3.104 Dashboard Shows Zero Campaigns

Open Campaigns and confirm:

1. A Campaign exists.
2. It belongs to the signed-in user.
3. Campaign creation completed successfully.
4. The Campaign was not deleted.
5. The user is not viewing only a shared Campaign.
6. The Dashboard was refreshed.

Dashboard Security

3.105 Protecting Dashboard Information

The Dashboard can reveal:

Do not leave it visible on an unattended shared screen.

3.106 Screenshots

Before sending a Dashboard screenshot:

1. Hide private Lead names.
2. Hide telephone information where visible.
3. Avoid exposing account identifiers.
4. Remove browser tokens or callback parameters.
5. Confirm the recipient is authorized.
6. Include the time of the issue.
7. Explain which metric appears incorrect.

3.107 Logging Out

After reviewing the Dashboard on a shared device:

1. Open the user menu.
2. Select Logout.
3. Confirm Login opens.
4. Close the browser window.
5. Log out of Google where required.

Closing the Dashboard tab alone may not remove the saved session.

Dashboard Review Checklists

3.108 Dashboard Access Checklist

Confirm that:

1. Dashboard opens after login.
2. The loading indicator disappears.
3. Four summary cards appear.
4. The seven-day chart appears.
5. Recent Activity appears.
6. Leads, Agents, and Campaigns cards appear.
7. New Campaign opens Campaigns.
8. View all logs opens Call Logs.

3.109 Metric Checklist

Confirm that:

1. Total Calls is understood as Call Log count.
2. Success Rate is understood as completed-call percentage.
3. Total Leads is understood as Lead-record count.
4. Contacted means a Lead-linked Call Log exists.
5. Uncontacted means no Lead-linked Call Log exists.
6. Talk Time is displayed in whole minutes.
7. The seven-day chart counts all Call Logs by creation day.
8. Recent Activity is limited to five entries.

3.110 Calling-Readiness Checklist

Before starting a Campaign, confirm:

1. Account is active.
2. Plan or trial is available.
3. Usage limits are understood.
4. Leads exist.
5. Lead numbers are valid.
6. Consent has been reviewed.
7. AI Agent exists.
8. Agent has been tested.
9. Knowledge Base is accurate.
10. Phone Number or SIP Trunk is available.
11. Provider credentials work.
12. Caller ID is correct.
13. Campaign schedule is correct.
14. Time zone is correct.
15. Calling hours are permitted.
16. Recording requirements are addressed.
17. A controlled test Campaign has succeeded.

3.111 Performance-Review Checklist

After Campaign activity, confirm:

1. Total Calls increased as expected.
2. Call volume appears on the correct day.
3. Completed-call rate is reviewed.
4. Failed statuses are investigated.
5. Busy and no-answer patterns are reviewed.
6. Talk Time is reasonable.
7. Contacted Leads are not mistaken for successful conversations.
8. Transcripts are reviewed.
9. Qualification outcomes are reviewed.
10. Appointments are confirmed.
11. Follow-up Leads are identified.

Chapter Completion

At the end of this chapter, the user should understand how AIUNIFY Assistant calculates and displays Total Calls, Success Rate, Total Leads, contacted Leads, uncontacted Leads, and Talk Time; how to interpret the seven-day call-volume chart; how to read Recent Activity and call-status badges; how the Dashboard differs for normal users and Super Administrators; why Dashboard totals may not include every shared resource; how to determine whether the account is operationally ready; and how to troubleshoot missing, delayed, or unexpected metrics.