Scoro AI – ELI assistant use cases and prompt examples

ELI assistant is far more than a simple Q&A chatbot – it is an active, highly capable ‘coworker’ built directly into your Scoro workspace. It can handle a wide range of tasks across project management, business operations, and everyday administration. Instead of just asking ELI questions, use it as an action-oriented assistant: delegate complex administrative tasks, challenge it to spot hidden patterns across your business, and combine multiple instructions into a single prompt.

This article contains practical, real-world use cases and prompts designed to help you get the most out of ELI assistant – the AI-powered assistant on your site. As you explore the example prompts below, think of all the things ELI could do for you and your team,  rather than just asking it to look up static information.

We are constantly shipping new tools and capabilities to the ELI assistant. If it cannot handle a specific workflow today, it might very well be able to do it tomorrow!

1. Use cases and prompt examples

The opportunities of using the ELI assistant are endless – below are some ELI example prompts that you cn start with:

• Manage your own work
• Managing schedules and calendar conflicts
• Resource planning, booking, and allocation
• Monitor your team’s work
• Time tracking
• Project management and progress tracking
• Scoro product support

1.1. Manage your own work

• Prioritize your work: "What should I focus on today?"
• Review your week: "Give me an overview of my schedule for this week based on my tasks and calendar."
• Identify workload issues and reschedule tasks: "I’m overworked. Help me prioritize and flag what could be rescheduled."
• Identify pending questions or mentions: "Is anyone waiting on me? Check comments across my tasks and projects from the past 2 weeks."

1.2. Managing schedules and calendar conflicts

• Identify calendar gaps: "Do I have any scheduling conflicts in my calendar this month?"
• Reschedule a recurring meeting series: "Move our weekly team sync from Tuesday mornings to Thursday afternoons starting next week."
• Find an open window on a colleague's busy day: "Scan Jane's and Oliver’s calendars for this Friday and find any 1-hour slots where they are free for a chat."
• Coordinate meetings that respect working hours across time zones: "Suggest a time to meet with Mark next week that isn't before 9 AM or after 5 PM in either of our time zones."

1.3. Resource planning, booking, and allocation

• Fill resource gaps: "Which of the in-progress projects are still missing doers?"
• Check availability: "Which bookings currently overlap with any time off?"
• Reallocate bookings for team member leave: "Split Mark’s bookings since he’s taking the last week of July off, and find another person with availability that week to cover him."
• Evaluate project feasibility based on team capacity: "Based on my team’s current bookings and availability over the next 6 weeks, is this project doable? If not, which role doesn’t have enough availability?" For the best results, ask this from the respective quote view.
• Simulate capacity limits for upcoming quarters: "Do we have the capacity to take on 20% more work in the next two quarters, or where would we hit a wall?"
• Split bookings and temporarily assign them to a placeholder role: "I will be on vacation from July 10-15. Please split my active bookings on Project X for those dates, and temporarily assign that chunk to a project manager role placeholder."

1.4. Monitor your team’s work

• Audit overdue work: "Give me a list of all overdue tasks assigned to my team."
• Review your team’s time logs: "Who hasn't logged time on this project this week?"
• Monitor team utilization: "Which users have logged less than 30 hours this week?"
• Automate follow-ups: "Add a comment to all overdue tasks on this project asking for a status update."
• Prompt owners of long-overdue tasks to close them: "Find all open tasks that are long overdue on this project and send notifications to the responsible owners to close them."
• Identify inactive projects and nudge the team: "Which of my active projects have gone quiet this week? → Add a comment on each one nudging the team to update progress or flag blockers by the end of Friday."

1.5. Time tracking

• Log time instantly: "Log 2 hours for today under task X for project Y."
• Check time-logging accuracy for timesheets: "Do I have any tasks due this week that I’ve logged time for, but the total is well below the planned hours?"
• Audit completed tasks with zero time logged: "Please show any tasks marked done where I logged zero time."

1.6. Project management and progress tracking

• Forecast deadlines: "Based on our current progress on this project, are we going to meet the deadline?"
• Update project status: "Mark all tasks under this project as done."
• Track daily project progress: "What progress has been made on my projects in the last 24 hours?"
• Catch up on project activity: "Summarize comments and activity on this project from yesterday."
• Identify stagnant projects: "Which projects have seen no activity in the last 14 days?"
• Surface high-risk projects: "Which projects are at the highest risk right now?"
• Deep-dive into bottlenecks: "Assess the project health and bottlenecks." → "Schedule a standup for the project team tomorrow at 10 am to discuss the bottlenecks and list the highlighted issues as agenda points."
• Summarize project risks for client reporting: "Summarise the risks and bottlenecks on Project X that I should flag to the client today."
• Clean up and update historical task records in bulk: "Mark all tasks created before July 1st as ‘Closed’, except the ones still ‘In Progress’, which should be flagged ‘Needs Review’ for me to look at."
• Gather project comment history to evaluate progress: "Pull together the recent comments across all tasks on this project to see how it’s progressing."
• Link project tasks to a quote for accurate tracking: "Link all the project’s tasks to Quote X using tasks’ activity types and the quote’s product names to match everything." This prompt is useful when you’ve set tasks via a project, not a quote, but need accurate calculations in the Quoted vs Actual table.

1.7. Financial analysis & business insights

• Analyze client profitability: "Which clients brought in the most revenue last year?"
• Audit project financial data: "Are there any bills not linked to projects yet?"
• Identify clients with over-budget projects: "Which clients have the most projects that ran over budget in the last 6 months?"
• Compare quarterly business performance: "How does our business health this quarter compare to last quarter?"
• Analyze profit margins by service type: "Which of our services have the healthiest margins, and which have the worst?"
• Check pipeline health: “How’s my pipeline doing?”

1.8. Scoro product support

• Get answers to questions about Scoro: ELI assistant is connected to Scoro’s Help Center, so it knows everything there and can help you with simple Scoro-related questions.

2. Best practices & pro tips

Here are a few cool tips you can use to get the most out of the ELI assistant:

• Ask ELI to share insights and reports via comments.
  • While sharing entire chats with other users on your site isn't possible yet, you can ask ELI to share the insights or reports it provided by adding them as a comment on the relevant project, task, or document on your site.
• Prompt ELI assistant from the relevant view.
  • ELI assistant is context-aware. For the best results, we recommend prompting from the relevant Scoro module or view – for example, triggering project analyses directly inside the project view, or feasibility checks directly from the respective quote view to give ELI the correct screen context.
• Get instant insights via ELI actions across various Scoro views.
  • The Bookings module, Calendar view, and the project header include ELI action buttons. These action buttons act as shortcuts to insights into the specific project's health or provide direct help with event and booking management. More action buttons are coming soon!