Forethought connector: Add AgentQA scored-tickets table
AnsweredConnector name:
Forethought
Table name:
AGENT_QA_SCORED_TICKET
API documentation link:
https://support.forethought.ai/hc/en-us/articles/51084067382803-AgentQA-Analytics-API
Note: The documentation may require authentication.
Additional details:
We are requesting a new table in the existing Forethought connector for human-agent QA results returned by the AgentQA Analytics API.
Fivetran Support confirmed that the current connector only uses the Forethought Solve Analytics API:
https://dashboard-api.forethought.ai/analytics/solve/v0
The existing connector does not call the AgentQA /scored-tickets endpoint. Its current AI_QA_INSIGHT table is populated from Solve conversation data and does not provide the human-agent custom-rubric results required for our use case.
We need the proposed table to include, where available:
- Ticket and agent identifiers
- Scored-ticket and evaluation timestamps
- Custom rubric and scorecard results
- Rubric criteria, labels, reasoning and scores
- Rubric weights and final weighted score
- Fields required to identify updated or re-scored evaluations
The integration should support Bearer-token authentication, pagination, incremental synchronization and upserts for updated or re-scored records.
Our business requirement is to ingest Forethought human-agent QA results into Snowflake and combine them with Salesforce Case QA data in a centralized reporting dashboard.
This request is time-sensitive because the AgentQA/custom-rubric API data has a rolling 90-day availability window. A managed connector would allow us to retain this history and avoid losing older QA results.
-
Official commentHi Taher,Thank you for the detailed request. We are currently reviewing the technical feasibility of adding a table for AgentQA scored-ticket results. We understand the urgency given the rolling 90-day data availability window, and we will update this thread as soon as our review concludes.Best,Syead Mujtaba Imam Rizwi
Please sign in to leave a comment.
Comments
1 comment