How can I use Frontline Intelligence?

Frontline Intelligence (FI) is Yourco’s AI reporting layer for leaders. It reads your organization’s employee communication history, survey results, and workforce data, then answers questions in plain language — with citations back to the original messages so you can verify every claim.

Use it in two ways:

1. Operationally — get a fast, accurate picture of what is happening with your workforce right now.

2. Trend Analysis — turn the same data into trends, before/after comparisons, and evidence you can use to quantify business impact and communicate results to leadership.

Who can prompt Frontline Intelligence?

How to get better answers

The quality of the answer follows the quality of the question. Use these rules every time.

Be specific. Name the person when the question is about someone, name the topic, and say what you want back (a count, a list of names from the messages, themes, or a comparison).

Always include a date or time frame. FI understands relative dates such as “today,” “yesterday,” “last week,” “last month,” and “year to date” in your organization’s timezone. Absolute dates (for example, June 1–June 30) are even clearer for reporting.

Ask for the output you need. “Summarize themes,” “list the people who texted about this,” “count how many,” and “compare this month to last month” produce very different, more useful answers than a vague question.

Stay in the same chat for follow-ups. After an answer, ask FI to drill in: “Show me the messages,” “Who were they?” “Break that down by week,” “What reasons did they give?”

Name people the way they appear in Yourco. If two employees share a name, FI may list the matches (including cell number) and ask which person you mean. If you are asking about that person’s messages, you can also say “search all of them.”

Weak vs. strong prompts

Part 1: Using FI day to day

These are the questions worth asking during a normal week. Replace {EMPLOYEE}, {START DATE}, {END DATE}, {SURVEY NAME}, and similar placeholders with your own details.

Attendance and call-offs

If the Call-Off Agent is set up for your account, FI reads structured absence records — date, category, reason, and days or hours — alongside the original texts. If it isn't set up, FI will tell you, and can still find absence mentions in messages.

• Who called off today?

• Who called off in the past two weeks? Include the date, category, and reason for each.

• How many times did {EMPLOYEE} call off between {START DATE} and {END DATE}?

• What was the most common call-off reason last week?

• Which employees called off more than once last month?

• How many partial-day absences did we have last week, and how many hours did they add up to?

• Did {EMPLOYEE} say they'd be late or leave early on {DATE}?

Announcements and confirmations

• Who confirmed receiving yesterday's company-wide announcement about {TOPIC}?

• Who hasn't replied to the message we sent on {DATE} about {TOPIC}?

• What questions did employees ask after we sent {ANNOUNCEMENT}?

• Summarize employee responses to last week's {TOPIC} message.

• Did {EMPLOYEE} acknowledge the schedule change we sent on {DATE}?

Safety

• Were there any messages about injuries, accidents, or near misses between {START DATE} and {END DATE}?

• What safety concerns have employees raised since {START DATE}?

• Did anyone report missing PPE, broken equipment, or an unsafe condition last week?

• Who confirmed receiving the safety alert we sent on {DATE}?

• Summarize what {EMPLOYEE} reported about the incident on {DATE}.

• What were the results of our last safety survey?

Surveys

• What surveys have we sent recently, and what were their response rates?

• What were the results of the survey sent last month?

• Show me results for {SURVEY NAME}. How many people were invited, how many submitted, and what was the response rate?

• Which questions on {SURVEY NAME} got the lowest or most negative responses?

• Is {SURVEY NAME} anonymous? Summarize the answers.

• For our last non-anonymous survey, list respondents and their answers to {QUESTION}.

Shift coverage

• Who volunteered for extra shifts between {START DATE} and {END DATE}?

• Who declined overtime offers last week?

• Summarize responses to the coverage request we sent on {DATE}.

• What shift-swap or scheduling requests came in this week?

• Did {EMPLOYEE} accept or decline the extra shift we offered on {DATE}?

Policy, training, and acknowledgments

• Who confirmed receiving the {POLICY OR HANDBOOK} we sent on {DATE}?

• Who hasn't confirmed the {COMPLIANCE TOPIC} message from {DATE}?

• What questions did employees ask about the new {POLICY}?

• Did {EMPLOYEE} acknowledge the training message from {DATE}?

Inbound questions and employee concerns

• What have employees been texting us about since {START DATE}? Group by topic.

• How many messages last month were about pay, paystubs, or missing hours?

• Which employees raised complaints or concerns last week? Summarize the themes.

• Summarize unanswered employee questions from yesterday.

• What concerns has {EMPLOYEE} raised since {START DATE}?

Emergencies, weather, and urgent notices

• Who replied to the closure message we sent on {DATE}?

• What did employees report about site conditions on {DATE}?

• Summarize inbound messages from {DATE} related to the outage.

• How quickly did employees confirm the emergency notice on {DATE}?

Looking up one person

FI looks people up by name. Once it finds them, it can show their details and pull their messages.

• What department, location, language, and tags does {EMPLOYEE} have?

• Is {EMPLOYEE} an Admin, Manager, or Employee in Yourco?

• Is {EMPLOYEE} still active, and are they still receiving messages?

• Show me {EMPLOYEE}'s messages from {START DATE} to {END DATE}.

• Summarize all messages with {EMPLOYEE} in the last 90 days.

Asking about yourself

FI knows who you are, so you can speak naturally.

• What's my department and location?

• What messages have I sent this week?

Part 2: Tracking trends over time

The same data becomes far more useful when you ask about change instead of a snapshot. A trend question has three parts: the thing you're measuring, the period you care about, and the period you're comparing it against.

How to phrase a trend question

Start with a normal operational question, then add one of these:

• "…and compare that to the previous 30 days."

• "…grouped by month from {START DATE} to {END DATE}."

• "…broken down by week."

• "…compared with the same period last year."

• "…before and after {DATE}, when we sent {ANNOUNCEMENT}."

Two tips that make trends more reliable: use absolute dates rather than relative ones when you want a clean comparison, and ask for month-sized windows when looking at absence data — FI pulls call-off records in chunks, and monthly slices give the cleanest picture over a long stretch.

Attendance trends

• Compare call-offs in {MONTH} with {PREVIOUS MONTH}. Did volume go up or down, and which categories changed?

• Group call-offs by month from {START DATE} to {END DATE}. What's the overall direction?

• Which call-off categories are the most common this quarter, and how does that compare to last quarter?

• Which employees have the most call-offs in the last 90 days? Include the count and reasons.

• Were call-offs concentrated on particular days of the week between {START DATE} and {END DATE}?

• After we communicated the new attendance policy on {DATE}, did call-offs rise or fall over the following 30 days?

• How did partial-day absences trend over the last three months?

Sentiment and retention-signal trends

• Compare employee sentiment in messages from {START DATE} to {END DATE} with the previous period. What improved, what got worse, and what new themes came up?

• List messages from the last 90 days where employees mentioned quitting, giving notice, or looking for other work. How does that compare with the 90 days before?

• How did scores and comments change between {PREVIOUS SURVEY NAME} and {LATEST SURVEY NAME}?

• After we announced {POLICY CHANGE} on {DATE}, what was the tone of replies over the following two weeks?

• Which concerns keep coming back in inbound messages this quarter?

Safety trends

• Group safety-related messages — injuries, near misses, hazards, PPE — by month from {START DATE} to {END DATE}. Is the trend up or down?

• After the {SAFETY CAMPAIGN} message on {DATE}, what safety issues did employees still report over the next 30 days?

• Compare safety survey results between {PREVIOUS SURVEY} and {LATEST SURVEY}. What improved?

• What safety concerns were raised this quarter that weren't raised last quarter?

Communication trends

• Compare reply and confirmation volume across our last three company-wide announcements.

• Which announcements last month generated the most follow-up questions or confusion?

Survey participation trends

• Which of our last 10 surveys had the lowest response rates, and what were they about?

• Compare the response rate for {SURVEY NAME} this time with the previous time we sent it.

• Across the pulse surveys we've sent this year, which themes keep recurring?

• Summarize open-ended comments from {SURVEY NAME} into themes, with example quotes.

Workload trends

• Compare inbound question volume by theme for {MONTH} versus {PREVIOUS MONTH}.

• After we sent the {FAQ} on {DATE}, did questions about {TOPIC} go down?

• What are the top inbound themes this month, and are they increasing or decreasing?

A cadence that works

Most teams settle into a rhythm like this.

Daily: Who called off today? What came in overnight? Any safety mentions in the last 24 hours? Any unanswered questions?

Weekly: Who called off this week, and why? What themes showed up in complaints or questions? What's the status of open surveys? Who volunteered or declined extra shifts?

Monthly: Compare this month's call-offs, sentiment themes, safety mentions, and survey participation with last month. Then ask FI to summarize what changed and what to watch.

For anything you plan to share outside your team, open the citations first so you can understand the underlying communications and data.