What type of reporting exists for coffee chats?

Hi ​@djvincent, Yes, reporting exists, but the level of detail depends on whether you’re using standard dashboards or Data Hub/custom SQL.

What’s available

1. Standard dashboard / in-product reporting

For higher-level usage, Mentorship/Networking analytics are available in the TM Feature Usage & Outcomes dashboard, specifically the Networking area. Existing documented metrics include things like employees open to mentoring/networking and connection request activity. Some customer-facing dashboard materials also reference usage/outcomes metrics such as “% of employees using networking,” “% of employees as mentors,” and “% of employees as mentees”.

That said, for detailed Coffee Chat lifecycle reporting — requests, accepts, declines, cancels, specific individuals — Data Hub is the better source.
 

2. Data Hub reporting

Coffee Chats can be reported from Data Hub using the profile_connection table, where Coffee Chat records are represented as type = 'basic'. You can report on:
 

• Total Coffee Chat requests
• Unique requesters
• Unique recipients
• Pending requests
• Active / accepted requests
• Ended requests
• Declined requests
• Cancelled requests
• Requests that were ever accepted, using accepted_at IS NOT NULL
• Request date, last updated date, accepted date, and end date

The current support guidance also confirms you can report on:

• Employees open to Coffee Chats, using the open_to_coffee_chats preference
• Coffee Chat request detail for all participants
• Coffee Chat request detail for non-alumni employees
• Coffee Chat usage summary by status

Can we report on how many Coffee Chats a specific individual has?

Yes. You can filter the Data Hub query by the person’s email or employee/profile ID and count:
 

• Coffee Chats they sent — where they are the requester / source_profile_id
• Coffee Chats they received — where they are the recipient / dest_profile_id
• Total involvement — sent + received
• Breakdown by status: pending, active, ended, declined, cancelled
• Accepted chats — accepted_at IS NOT NULL

Example pattern:

SELECT
  COUNT(*) AS total_coffee_chat_requests,
  SUM(CASE WHEN requester.employee_email = 'person@company.com' THEN 1 ELSE 0 END) AS sent_by_person,
  SUM(CASE WHEN recipient.employee_email = 'person@company.com' THEN 1 ELSE 0 END) AS received_by_person,
  SUM(CASE WHEN c.status = 'pending' THEN 1 ELSE 0 END) AS pending_now,
  SUM(CASE WHEN c.status = 'active' THEN 1 ELSE 0 END) AS active_now,
  SUM(CASE WHEN c.status = 'ended' THEN 1 ELSE 0 END) AS ended,
  SUM(CASE WHEN c.status = 'declined' THEN 1 ELSE 0 END) AS declined,
  SUM(CASE WHEN c.status = 'cancelled' THEN 1 ELSE 0 END) AS cancelled,
  SUM(CASE WHEN c.accepted_at IS NOT NULL THEN 1 ELSE 0 END) AS ever_accepted
FROM profile_connection AS c
LEFT JOIN employee AS requester
  ON requester.profile_id = c.source_profile_id
LEFT JOIN employee AS recipient
  ON recipient.profile_id = c.dest_profile_id
WHERE c.type = 'basic'
  AND (
    requester.employee_email = 'person@company.com'
    OR recipient.employee_email = 'person@company.com'
  );

One important caveat

The user-facing Coffee Chat dashboard may not show every historical request. For example, cancelled Coffee Chat requests are intentionally not shown in the user’s “Sent” list, but they do remain visible in reporting and can be used as the audit trail. So if the goal is complete reporting, use Data Hub rather than relying only on the UI.