Understanding the Climenos workflow

How customer records connect to services, work, payments and reports.

View as Markdown

Understanding the Climenos workflow

The customer is the starting point. Their profile holds contact and website details and provides the context for services, money, documents and communication.

Recurring work and money

Add maintenance, hosting, domain, support or a custom service to a customer. Its price, VAT, payment status and dates feed Renewals. When a payment is recorded, Payment History preserves its date, amount and related service; invoice documents can be associated with that record. Finance gives the wider business view. An Offer is a separate proposal: prepare and send it, then update the customer's services or project as appropriate when work is agreed.

Website and reports

The customer's website can be paired with Climenos Connector. The connection supplies site and maintenance information used in the customer view and in Reports. Google analytics and search data require their own connection and customer mapping; a working Connector alone does not imply those reports are available.

Projects and support

Projects organise a website build into tasks and subtasks. You can expose relevant work to the customer, collect comments and move work through review and revisions. Tickets are conversations about support. When support time or billable work is recorded, it can update the customer's support-hour balance or payment record, depending on the support arrangement.

These are related records, not automatic substitutes for one another. Finishing a project does not by itself mean an invoice has been issued or a payment recorded. Confirm each step in its own area.

See Customer profiles, Renewals, Projects and Support tickets.

Still need help?

Use this area later for support, feedback or “Was this helpful?”.

Contact Support →