Notes: Customer Context for Cloud Teams

Overview

Notes in Spotto give teams a shared place to capture customer context, requirements, objectives, and engineering observations. They are designed for the information that usually lives in someone's head, a ticket comment, a meeting transcript, or a document nobody remembers to open.

Use Notes to align cloud work with what the customer actually cares about, and to give Spotto Chat better context when it answers questions about that customer.

Feature overview

Cloud data explains what exists and what changed. Notes explain why it matters.

The Notes page lets you store structured customer context next to general notes and meeting notes. This makes it easier for engineers, service delivery managers, FinOps specialists, security reviewers, and customer-facing teams to work from the same source of truth.

Notes can help capture:

• customer goals and business priorities
• cloud objectives and operating constraints
• security, architecture, operations, FinOps, performance, reliability, and roadmap context
• meeting notes and follow-up actions
• decisions, assumptions, and known exceptions
• useful public company information when Company Profile research is allowed

That context can then support Ask Spotto, reporting, reviews, recommendations, and handovers. It is not a replacement for tickets, change records, or architecture decision records, but it is a good place to keep the customer story close to the cloud data.

Why use this? (Jobs, pains, gains)

Jobs to be done

• When I am reviewing a customer environment, I want to see the customer's objectives and constraints, so I can interpret recommendations in the right context.
• When I am asking Spotto Chat a question, I want the assistant to understand saved customer context, so answers are not based on telemetry alone.
• When another engineer has already learned something about the customer, I want that knowledge to be visible by topic, so I do not have to rediscover it in a call, ticket, or chat thread.
• When I am preparing a review, report, or action plan, I want to align cloud work to customer outcomes, so recommendations are easier to prioritize and explain.

Common pains this fixes

• Customer context is scattered across tickets, calls, documents, and individual engineers.
• Recommendations can look technically correct but miss the customer's real priorities.
• Engineers repeat discovery work because earlier context was never written down.
• Handover quality depends too much on who happens to be online.
• AI chat answers are less useful when the assistant only sees cloud signals and not the customer's goals.

What you gain

• A central place for customer-specific context that lives with the rest of the Spotto workflow.
• Better customer alignment when reviewing security, reliability, cost, performance, and roadmap work.
• Less knowledge silo risk when engineers change shifts, teams, or accounts.
• More useful Spotto Chat responses because saved context can ground follow-up questions.
• Cleaner preparation for customer reviews, QBRs, reporting, and remediation planning.

Key capabilities

Where to find it

In the Spotto Portal, open a company and navigate to Notes.

The page is company-scoped. Notes are saved against the selected company, so always confirm you are in the right customer context before adding or applying information. Yes, that sounds obvious. It is still how bad notes happen.

Capture structured Customer Context

Customer Context notes are organized into built-in topics so teams can record information consistently:

• Company Profile: who the company is, what they do, and public research or source links
• Security: security objectives, risk posture, compliance drivers, and control priorities
• Architecture: platform design, constraints, dependencies, and standards
• Operations: operating model, support expectations, maintenance windows, and ownership
• FinOps: cost priorities, budgets, commitment strategy, and optimization preferences
• Performance: performance expectations, workload sensitivity, and known bottlenecks
• Reliability: availability targets, recovery expectations, backup posture, and resilience risks
• Roadmap: planned changes, migrations, renewals, and strategic initiatives

Each topic gives engineers a predictable place to look. If a security specialist needs security context, they should not have to read six meeting notes and guess which one mattered.

Store General and Meeting notes

Use General notes for free-form context that does not fit a structured Customer Context topic yet.

Use Meeting notes to record discussion points, action items, decisions, and follow-up context from customer or internal meetings. Meeting notes are useful when the discussion happened before the team knew where the information should live permanently.

As a rule of thumb:

• Put stable customer context in the relevant Customer Context topic.
• Put temporary discussion history in Meeting notes.
• Put one-off observations or drafts in General notes.

Use Ask AI to draft note content

Where AI chat is enabled for the company and your role can manage Notes, Notes can show Ask AI controls.

Ask AI can help draft or improve notes from the context already available in Spotto. For structured Customer Context notes, section-level Ask AI can focus on one topic area rather than rewriting the whole page.

Use AI suggestions as drafts. Review them before applying them. Accepted suggestions are saved through the Notes save flow. The goal is to reduce blank-page work, not to outsource customer knowledge to a sentence generator with a nice button.

Research Company Profile with explicit internet search

Company Profile can optionally use public internet search when you enable Allow internet search for that request.

This is off by default. When enabled, Spotto can look up public company information and return source links so you can review what was used before applying it.

Use this for public facts such as company website, industry, products, services, or public positioning. Do not put private customer data into the prompt just to make a public lookup more convenient.

Feed saved context into Spotto Chat

Saved Customer Context notes can help Spotto Chat answer better questions about the current customer.

For example, if the Security context says the customer is preparing for an audit, then a security recommendation is not just another control item. It has timing, stakeholder, and risk context. The same applies to FinOps constraints, reliability targets, roadmap dependencies, or operational ownership.

This is where Notes become more than documentation. They help the assistant reason with the current customer's priorities, not only the current customer's telemetry. Saved note context is scoped to the active company you are viewing; it is not pulled from other companies even if you can access them.

Suggested workflows

Start with Company Profile

For a new customer, begin with the Company Profile note:

1. Capture what the company does.
2. Add website and public source links where useful.
3. Record products, services, regions, or operating details that help engineers understand the customer.
4. Save the note once the information is reviewed.

This gives future notes a basic identity layer.

Build out topics during reviews

During reviews or onboarding, fill in the topic areas that matter first:

1. Use Security, FinOps, Reliability, or Operations for active review themes.
2. Add the customer's objectives, constraints, and known exceptions.
3. Link observations back to recommendations, review checklists, or reports where useful.
4. Keep the wording practical enough that another engineer can act on it later.

Turn meeting notes into durable context

After a customer meeting:

1. Save the discussion as a Meeting note.
2. Move stable facts into the relevant Customer Context topic.
3. Keep action items in the system your team uses for work tracking.

The meeting note records the conversation. Customer Context records the durable knowledge.

Use notes before asking broader AI questions

Before using Spotto Chat for prioritization or planning questions, check that the relevant context exists:

• customer objectives
• known constraints
• security and compliance priorities
• budget or commitment preferences
• operational ownership and maintenance expectations
• roadmap or migration timing

Better context usually means better answers. This is one of the few places where "write it down" is genuinely a product feature.

Technical reference

Component	Details
Inputs	User-authored Customer Context, General notes, Meeting notes, optional AI-generated drafts, and optional public Company Profile research when explicitly allowed.
Outputs	Saved company-scoped notes, structured Customer Context by topic, note previews, and context that can support Spotto Chat and related workflows.
AI controls	Ask AI is available only when the company and user can use the AI chat feature and the user has permission to manage Notes. Company Profile internet search requires an explicit per-request opt-in.
Access control	Notes are scoped to the selected company and respect Spotto Portal access permissions. Users need the relevant Notes permissions to view or manage notes.
Best fit	Customer objectives, requirements, operating context, cloud priorities, review preparation, handover context, and topic-specific engineering knowledge.

How it differs from tickets and documents

Tickets are for work tracking. Documents are for longer-form deliverables. Notes are for customer context that should be easy to find while working in Spotto.

Use Notes when the information should:

• help interpret recommendations or cloud posture
• be reused across reviews and conversations
• help another engineer understand the customer faster
• shape AI-assisted investigation and reporting
• stay close to the company record rather than living in a detached file

Use your ticketing system for assigned work, due dates, approvals, and implementation tracking. Use formal documents for customer-ready deliverables. Use Notes for the context that helps both of those make sense.

How it works (high level)

• You open the Notes page for a company.
• You choose a Customer Context topic, General note, or Meeting note.
• Spotto saves the note against that company.
• Structured Customer Context topics keep related information in predictable sections.
• Ask AI can draft proposals when AI chat access and Notes manage permission are available.
• Saved Customer Context can be used by Spotto workflows that need customer-specific grounding.

Security and data handling

Notes can contain sensitive customer context, so treat them like operational records, not scratch paper.

• Access is company-scoped and controlled through Spotto Portal permissions.
• Ask AI for Notes follows the same AI chat access gate as Ask Spotto and also requires Notes manage permission.
• Public internet search is only available for Company Profile and only when explicitly enabled for the request.
• Public research should be used for public company facts, not private customer data.
• Review AI suggestions before applying them, especially when the note influences customer recommendations or reporting.

Limitations

• Notes are only as useful as the quality of what the team records.
• AI suggestions are drafts and should be reviewed before saving.
• Public Company Profile research depends on the company's website and available public sources.
• Notes do not replace tickets, change approvals, customer deliverables, or formal architecture decision records.
• If a user does not have access to the company or Notes feature, the page or actions may not be visible.

Troubleshooting

I cannot see Notes

What you're seeing: The Notes page is not visible in the Portal navigation.
Likely causes:

• You are in the wrong company context.
• Your role does not include Notes access.
• The feature is not enabled for that company. How to fix:

1. Confirm you are viewing the correct company.
2. Ask a company administrator to check your access.
3. If access looks correct but the page is still missing, contact support with the company name and a screenshot.

By default, Notes access is granted to Portal Administrator, Company Administrator, Company Hierarchy Administrator, and Service Delivery Manager roles. Company Viewer, Customer Portal Viewer, and Accounts Administrator do not include Notes permissions by default.

Ask AI is not visible in Notes

What you're seeing: You can edit or view notes, but there is no Ask AI button.
Likely causes:

• AI chat is not enabled for the company.
• Your role can view Notes but cannot manage Notes.
• Your role can manage Notes but cannot use AI chat.
• The selected note type or state does not support AI suggestions. How to fix:

1. Confirm Ask Spotto is available elsewhere for the same company.
2. Ask an administrator to check both AI chat access and Notes manage permission for your role.
3. Continue editing manually if AI chat access is intentionally disabled.

Company Profile research asks for a website

What you're seeing: AI says to add the company website before it can research the profile.
Likely cause: Public research needs a reliable company website so it can search for the right organization instead of guessing from a name. How to fix:

1. Open the company details page.
2. Add or correct the company website.
3. Return to Notes and retry the Company Profile request with Allow internet search enabled.

Notes feel duplicated across topics

What you're seeing: The same customer context appears in several notes.
Likely causes:

• Meeting notes were never distilled into Customer Context.
• A broad General note now belongs in a specific topic. How to fix:

1. Keep the original Meeting note if it records useful history.
2. Move stable facts into the right Customer Context topic.
3. Use General notes only for context that does not have a clear home yet.

Optimize Your Azure Environment

Looking to enhance your cloud setup for cost efficiency, performance, reliability, or security?

Talk to a cloud specialist. Email us or schedule a 30-minute consultation and let's optimize your cloud environment together.

Book a Free Consultation