-
Notifications
You must be signed in to change notification settings - Fork 0
Reporting and Admin Screens
The admin app is where the plugin becomes useful day to day.
I do not want a pile of raw tables. I want reporting surfaces that help me move from a trend to the underlying record quickly.
The dashboard is the quickest summary view of what is happening.
It already surfaces:
- high-level metrics
- recent top pages
- engaged traffic trends
- call-intent summaries
- commerce-interest signals
- shortcuts into saved reporting segments
- sample-data controls
The sessions screen is for understanding individual journeys and filtered traffic patterns.
I can use it to:
- search by terms and date range
- review attribution and engagement context
- inspect confidence and source/provider patterns
- export the current filtered view
- open a single session detail view
The session detail view can now include linked call context and stronger commerce-interest summaries.
The companies screen builds on enrichment and repeat-visit behaviour.
It helps me identify:
- recurring business traffic
- likely organisations behind visits
- session volume and recency
- call activity connected to those companies
- stronger priority leads worth follow-up
Company names link into detail views, and the detail screens now include recent call context so I do not have to bounce back and forth constantly.
The calls screen is the current reporting layer for stored call records.
It includes:
- call summaries and charts
- top call-driving pages
- matched and unmatched call filtering
- imported Amazon Connect call filtering and source visibility
- CSV export of the filtered view
- linked drilldowns into sessions, companies, and numbers
- a single call detail view for focused review
The chats screen is the reporting surface for stored frontend assistant conversations.
It gives me:
- a list of captured frontend chat conversations
- transcript drilldowns
- queue-style filters for status, owner, priority, provider, model, and commercial workflow state
- linked workflow fields such as outcome, follow-up date, notes, and owner assignment
- live handover controls so I can let the AI continue, take the chat over manually, or end it
- operator reply suggestions from the assistant when I want help phrasing a human answer
- live typing visibility and fresher relative timestamps while I am reviewing a single chat
- links back to related sessions and matched companies where available
- filtered export for follow-up or review
This is useful now that the assistant is grounded in company, product, and shipping context, because I can see what people are actually asking before I decide what to tune next.
The phone numbers screen now behaves like a setup page rather than a raw report.
That means I can:
- add new numbers cleanly
- edit routing rules
- review defaults and active/inactive numbers
- jump into a number detail view
- keep Amazon Connect identifiers with the number configuration
The WooCommerce reporting view does not try to replace order analytics.
Instead, it focuses on interest and repeat attention:
- top products
- top categories
- repeat-interest patterns
- linked sessions and companies showing those signals
- filtered export for review elsewhere
Saved segments let me preserve useful filter combinations across:
- sessions
- companies
- calls
- WooCommerce reporting
- chats are still a working queue with richer workflow controls rather than a saved-segment-first reporting surface
The dashboard can then expose shortcuts back into those saved views, which makes repeat analysis much quicker.
The admin app now leans on route-based takeover views for single records. That keeps the main content focused on the selected session, company, call, number, or chat while the right-hand column carries supporting context and workflow controls.
Single-record views are now much more consistent:
- back navigation sits in a clearer top-left position
- the main body carries the transcript or record detail
- the right-hand sidebar carries workflow, related data, and summary context
- section-title treatment is trimmed back on single-record screens so the content itself stays central
The same principle carries into the frontend assistant too: the first matched source is shown more prominently, and any additional source options stay collapsed until expanded.