> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lynkacrm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What to check in Lynka each morning

> Use Lynka as a small business control room by reviewing money, customers, today’s work, stock, support, approvals, and performance in a practical order.

A good morning in Lynka should not begin with opening every product area and looking for problems manually.

Start with what needs attention, then go deeper only where the business is asking for action.

## 1. Money that needs attention

Check overdue and due-soon Invoices, recent Payments, supplier Bills, payables, and any cash or bank work that needs review.

The question is simple: **Is money expected to move today, and is anything late?**

If the business uses Accounting, also check exceptions that could prevent clean financial reporting or period close.

## 2. Customers that need attention

Review active Leads and Deals with overdue follow-up, no next step, approaching close dates, or other attention signals.

LeadGen is useful when it feeds work the team can actually follow up. If the team already has a backlog of untouched generated Leads, solve the follow-up problem before generating another large list.

## 3. Today's activities

Review calls, meetings, tasks, and reminders. The Activity view is the operational bridge between a record existing and somebody doing something about it.

## 4. Stock and purchasing problems

If you sell products, review low stock, out-of-stock items, open or overdue Purchase Orders, partial receipts, damaged quantities, and received stock that is still on hold.

These are more useful morning signals than staring at total inventory value without context.

## 5. Customer support risk

Review unassigned Tickets, tickets waiting for first response, SLA risk, SLA breaches, and unusually idle or repeatedly reopened tickets.

The goal is to catch service problems before the customer has to chase you again.

## 6. Approvals and exceptions

Owners and managers should review items that need a decision, not redo everybody's work.

Use approvals, owner attention surfaces, and automation to surface the exceptions where a second decision matters.

## 7. Performance after action

Once today's problems are understood, use the Dashboard and Reports to answer wider questions about pipeline, revenue, margin, inventory, campaign performance, support, and finance.

Charts are valuable when they help decide what to do next. They should not replace the operational review.

## Make the dashboard reflect responsibility

A salesperson's useful dashboard is not the same as the owner's. A finance user's dashboard should not be dominated by marketing widgets. A support user should see service work rather than irrelevant inventory metrics.

Lynka's configurable dashboard and access model allow each person to focus on the work they can actually see and perform.

## Small team habit

A five-person company does not need a long daily meeting to coordinate every record. If ownership, activities, attention rules, and reporting are accurate, the system can answer most status questions before the meeting begins.

That is the operating habit Lynka should support: **see what needs attention, do the work, then use reporting to understand what changed.**