Solstice Platform Instructions Guide

Powered by CelestiQ
Applies to: Solstice web, desktop, and mobile experiences
Last updated: July 27, 2026

What Solstice Is

Solstice is a secure AI intelligence platform for research, connected knowledge, product discovery, technical analysis, and decision support. Your organization may give the assistant a custom name and may configure which data sources, tools, and modes are available.

The platform is conversation-based: ask a question in natural language, add files or other context when useful, and refine the result through follow-up questions. Conversations are saved independently so you can return to a topic without rebuilding its context.

The Most Important Change: Start with Application Expert

Application Expert is the default and recommended mode for most work. It is no longer limited to simple questions about one internal knowledge base. It is designed to understand your intent, select the appropriate tools, and coordinate research across the sources available to your organization.

Use Application Expert when you are unsure which mode to choose. It can support:

• Application and engineering questions
• Cross-referencing multiple documents or sources
• Part and component lookup
• Company and market research
• Pricing and sourcing research
• Technical comparisons and tradeoff analysis
• Requirements analysis
• Troubleshooting and root-cause investigation
• Multi-step research and dynamic workflow planning
• Summaries, tables, recommendations, reports, and file generation

You do not need to tell Application Expert which internal tool to call. Describe the outcome you need, the relevant constraints, and the form the answer should take. The platform analyzes the request, routes work through the appropriate search or knowledge pipelines, and combines the results into one response.

Quick Start

1. Sign in and open New Chat.
2. Leave the mode set to Application Expert unless your task clearly fits a focused mode.
3. Ask a complete question. Include the objective, context, constraints, and desired output.
4. Attach supporting files when the answer depends on a datasheet, drawing, spreadsheet, presentation, image, or other document.
5. Review the answer, sources, assumptions, and any stated uncertainty.
6. Ask follow-up questions in the same chat to refine the work.
7. Use the thumbs-up or thumbs-down controls to provide feedback.
8. Rename the chat or move it into a folder so it is easy to find later.

How Application Expert Works

Application Expert follows an intent-driven workflow:

1. Understands the request. It identifies the objective, entities, part numbers, technical parameters, dates, constraints, and requested deliverable.
2. Plans the work. For complex questions, it can divide the request into research, comparison, calculation, validation, and presentation steps.
3. Selects sources and tools. Depending on your organization's configuration, it can retrieve from private company knowledge, uploaded files, structured product data, approved web sources, and specialized search services.
4. Retrieves in parallel. The next-generation query engine can use multiple retrieval pipelines at the same time instead of relying on a single search path.
5. Cross-references evidence. It compares relevant facts, resolves or highlights conflicts, and connects information from multiple sources.
6. Builds the response. It organizes the findings into the format most useful for the request, such as a concise answer, decision table, shortlist, procedure, report, or generated file.
7. Maintains conversation context. Follow-up questions can build on earlier messages and files in that chat.

Automatic tool selection does not mean every answer uses every source. The assistant chooses sources based on the question and the capabilities enabled for your organization. If a particular source matters, say so explicitly—for example, “Use only the attached specification,” “Check our company knowledge base,” or “Include current market availability.”

Choosing a Mode

Select the current mode from the mode control near the top of the chat. Mode names and availability are configured by your organization, so your list may differ.

Practical mode rules

• Start in Application Expert for any task that mixes technical knowledge, documents, research, sourcing, or decision-making.
• Use Product Search when the main goal is to return products from the internal company catalog that meet defined requirements.
• Use QuantiQ Search when the main question is about the external electronics market, such as distributor inventory, current price, or availability.
• Use General Use for work that should not depend on private company knowledge.
• If the interface says Not using [Company] Knowledgebase, the selected mode is intentionally operating without that private source.
• You can switch modes during a conversation, but start a new chat when the subject, customer, project, or confidentiality context changes substantially.
• The platform records mode usage with messages and transcripts, which helps preserve context and supports analytics.

How to Ask Better Questions

You do not need special commands or prompt syntax. A strong request usually contains five elements:

Goal + context + constraints + evidence + output format

Basic template

I need to [goal].

Context: [application, customer, project, or business situation].
Requirements: [technical, commercial, timing, compliance, or geographic constraints].
Use: [company knowledge, attached files, current market data, web sources, or specified sources].
Return: [answer format, level of detail, comparison criteria, and recommendation].

Weak versus strong questions

Weak:

What part should I use?

Strong:

Recommend three parts for a 24 V industrial control enclosure. The part must operate from -20 °C to 70 °C, fit within a 35 mm mounting depth, and have the required agency approvals. Use our product knowledge and explain why each option qualifies. Return a comparison table and identify any requirement that cannot be verified.

Weak:

Compare these PDFs.

Strong:

Compare the attached datasheets for electrical ratings, operating temperature, dimensions, certifications, lifecycle status, and stated limitations. Cite the source for every material claim. Put conflicts or missing values in a separate “Needs verification” section and recommend the better fit for outdoor industrial use.

Useful instructions to add

• “Ask me questions before recommending anything if a required parameter is missing.”
• “Separate verified facts from assumptions.”
• “Cite each technical claim and link to the original source when available.”
• “Use only the attached files.”
• “Use our internal knowledge plus current external sources.”
• “Compare at least three alternatives using the same criteria.”
• “Do not treat a distributor listing as proof of manufacturer specifications.”
• “Return a short executive summary followed by the engineering detail.”
• “Show calculations, units, and conversion assumptions.”
• “Identify conflicts between sources rather than silently choosing one.”
• “State the date of any price, inventory, lead-time, or lifecycle information.”
• “Create a downloadable report/spreadsheet/presentation after the analysis.”

Prompt Library

Application and engineering question

In Application Expert, explain whether [product/technology] is suitable for [application]. Consider [operating conditions], [performance requirements], [standards], and [installation constraints]. Use company knowledge and the attached files. Cite the evidence, list assumptions, identify risks, and finish with a clear recommendation.

Cross-reference multiple sources

Cross-reference the attached specification, datasheet, and test report. Build a requirement-by-requirement compliance matrix with columns for requirement, source evidence, pass/fail/unknown, and notes. Call out contradictory values and do not infer compliance where the evidence is missing.

Part lookup

Find the exact specifications and lifecycle information for part number [part number]. Confirm the manufacturer and ordering code first. Return key specifications, compatible accessories, certifications, known constraints, and source citations. If multiple products share the number, stop and ask me to disambiguate.

Product selection

Use Product Search to find products for [application]. Required criteria: [list]. Preferred criteria: [list]. Exclude: [list]. Return the best matches in a table, explain why each qualifies, and clearly mark any unverified requirement.

QuantiQ sourcing search

Use QuantiQ Search to compare current distributor availability for [manufacturer part number] in [region/currency]. Show distributor, stock, unit price at [quantity breaks], minimum order, lead time, and the date checked. Separate authorized from unverified sellers when that information is available. Include possible alternates but do not claim drop-in compatibility without validating specifications.

Company research

Research [company] for [business objective]. Cover products, target markets, locations, recent developments, competitors, and potential fit with our capabilities. Distinguish current external findings from internal company knowledge, cite material claims, and end with recommended next actions.

Pricing research

Research current pricing for [part/product] at quantities [list] in [currency and region]. Include the date checked, source, stock status, lead time, minimum order, and price-break assumptions. Flag stale, incomplete, or non-comparable listings and summarize the most defensible sourcing option.

Troubleshooting

Help troubleshoot [symptom]. System context: [details]. Expected behavior: [details]. Observed behavior: [details]. Changes already made: [details]. Evidence attached: [logs/images/files]. Rank likely causes, explain the evidence for each, and give me a safe step-by-step diagnostic plan before suggesting replacement parts.

Executive deliverable

Analyze the attached material and produce a one-page executive brief. Include the decision, supporting evidence, business impact, technical risks, unresolved questions, and recommended next actions. Keep the summary non-technical, then add a technical appendix with citations.

Working with Files

Use the attachment control beside the message field to add supporting material. The current platform supports common images, PDFs, Word documents, presentations, spreadsheets, CSV/TSV data, text, Markdown, JSON, HTML, XML, and other enabled technical document types.

• You can attach up to 10 files to one message.
• On mobile, choose Take Photo, Photo Library, or Choose Files.
• Wait for uploads and processing to finish before sending.
• Select an attachment chip or message attachment to preview it. Available preview or sharing options depend on the file type and device.
• Files remain available as context throughout the conversation, so follow-up questions can refer to “the attached datasheet” or a filename.
• For multiple files, identify each file's role and say how they should be compared.
• For spreadsheets, name the relevant sheet, columns, filters, or calculation you want.
• For images, say what to inspect—for example, a label, connector, damage pattern, schematic region, or measurement.
• For long documents, specify the sections, tables, pages, or requirements that matter most.

Do not assume that uploading a file automatically adds it to the organization's permanent knowledge base. A conversation attachment supplies context to that chat. Organization-wide ingestion and document management are separate administrative workflows.

Current Information, Web Research, and Citations

Application Expert can automatically select authorized current-information tools when a question requires recent external facts. Some organizations may also expose a separate Web Browsing control. Earlier platform versions required users to toggle web browsing or reasoning more often; the current Application Expert experience is designed to make that routing decision automatically.

For time-sensitive work:

• Say that current information is required.
• Specify the relevant date, country, region, currency, and quantity.
• Ask for source links and the date checked.
• Treat price, stock, lead time, laws, standards, lifecycle status, and company information as changeable.
• Ask the assistant to identify stale or conflicting sources.

When citations are provided, open the cited source and confirm that it supports the claim. A citation improves traceability but does not replace engineering, legal, financial, safety, or procurement review.

Continuing and Organizing Work

Conversations

• Each chat maintains its own history and context.
• Continue in the same chat when the follow-up depends on prior answers or attachments.
• Start a new chat for a new customer, project, product family, or unrelated objective.
• Conversations receive generated titles; rename them when a clearer project-specific title will help.
• Older legacy chats may remain visible but may not support continuation.
• Responses can continue processing in the background in supported experiences. Return to the chat to review the completed result.

Folders

• Create folders for customers, projects, product families, investigations, or recurring workflows.
• Move conversations into or out of a folder from the conversation options.
• Rename folders and use colors to make major workstreams easier to scan.
• On the web experience, folder transcript export can download the folder's conversations as a packaged set of branded PDFs.

Transcripts and outputs

• Copy response text or copy structured tables when the control is available.
• Download or export conversation transcripts from supported web/desktop controls.
• Ask Application Expert to turn completed research into a polished document, spreadsheet, presentation, diagram, or other supported file.
• Before sharing a generated deliverable, check the source data, calculations, citations, dates, and confidential content.

Voice, Read-Aloud, and Language

• Select the microphone beside the message field to dictate a question. Grant microphone permission when prompted.
• Review dictated text before sending, especially part numbers, units, acronyms, and names.
• Select the speaker/read-aloud control on an assistant response to hear it. Select it again to stop playback.
• On supported web/desktop experiences, voice options are available under Settings → General.
• Choose the interface language in Settings. You can also ask the assistant to answer or translate in a specific language.

Voice input is convenient for natural questions, but type or paste exact part numbers, formulas, serial numbers, and safety-critical values whenever possible.

Mobile App Instructions

The native Solstice mobile app provides the same core conversation model in an interface designed for iOS and Android.

Navigation

• Tap the history/menu control to open conversations and folders. On compact layouts, you can also swipe inward from the left edge.
• Tap the mode name in the header to view available modes and their descriptions.
• Tap the account control to open Settings.
• Pull down in the conversation list to refresh.
• Long-press a conversation to rename it, move it to a folder, or delete it.
• Long-press a folder to rename it, change its color, or delete the folder. Deleting a folder leaves its conversations under All Chats.

Mobile attachments and answers

• Tap + to take a photo, select from the photo library, or choose files.
• Tap an attachment to preview it; supported files can be shared through the device share sheet.
• Tap the microphone to dictate and the up-arrow to send.
• Use the down-arrow above the composer to jump to the newest message in a long chat.
• Use the controls below a response to copy, read aloud, like, or dislike it.
• Interactive visuals and generated images display inside supported responses.

Mobile settings and security

Settings includes appearance, accent color, language, notifications, user preferences, biometric unlock, offline-cache refresh, account controls, product information, changelog, instructions, terms/privacy, and service status.

• Biometric unlock protects an existing signed-in session with Face ID, Touch ID, fingerprint, or supported device biometrics. Solstice does not store your password or receive your biometric data.
• Notifications can alert you to supported response-completion, incident, maintenance, or product-update events, depending on deployment configuration and permissions.
• When the app reports that it is offline, saved conversation history may remain available. Check connection and synchronization status before relying on a newly sent message or attachment.
• Deleting the mobile app does not itself delete your Solstice account. Use Settings → Delete account for an account-deletion request.

Personalizing the Assistant

Open Settings → General/Preferences → User preferences to tell the assistant how you want responses written. These instructions apply to new chats together with available profile context such as your name, language, and company.

Good preference examples:

Be concise. Use tables for comparisons. Separate verified facts from assumptions and cite technical claims.

Write for an engineering audience. Show units and calculations, call out missing requirements, and end with recommended next actions.

Use preferences for stable communication choices, not one-time task requirements. Put customer details, project requirements, or special source restrictions in the relevant conversation.

Reviewing Answers and Giving Feedback

The assistant can make mistakes, misread source material, combine incompatible data, or present outdated facts. Review important work before acting on it.

For high-quality review:

1. Confirm that the assistant answered the actual question.
2. Check that part numbers, units, dates, quantities, regions, and currencies are correct.
3. Open citations and verify that they support the associated claims.
4. Distinguish manufacturer specifications from distributor or third-party statements.
5. Recalculate safety-critical or financially material values.
6. Confirm that unknowns are labeled rather than inferred.
7. Obtain appropriate professional or organizational approval.

Use thumbs up when a response is accurate and useful. Use thumbs down when it is wrong, incomplete, unclear, or poorly sourced, and add a short explanation when the feedback form is available. Specific feedback—such as “temperature rating came from the wrong variant” or “the source is three years old”—is more useful than a general negative rating.

Security and Responsible Use

• Use Solstice only for authorized work and data.
• Follow your organization's confidentiality, export-control, privacy, retention, and acceptable-use policies.
• Do not include passwords, private keys, authentication codes, or secrets in prompts or uploads.
• Confirm the correct organization or tenant before opening sensitive chats or uploading files.
• Treat generated output as decision support, not as an autonomous approval.
• Do not rely on the assistant as the sole authority for safety-critical engineering, medical, legal, financial, regulatory, or compliance decisions.
• Review generated files before distributing them outside your organization.

Customer files and company knowledge are handled within the organization's configured Solstice environment. Conversation attachments, private knowledge-base documents, and public web results are distinct source types; ask the assistant to label them when provenance matters.

Troubleshooting

The answer is too broad

Add the application, goal, requirements, exclusions, source scope, and desired format. Ask for a requirement-by-requirement answer.

The answer did not use company knowledge

Confirm that Application Expert or another knowledge-enabled mode is selected. Look for a notice that the current mode is not using the company knowledge base. Then ask explicitly: “Use our company knowledge base and cite the internal sources.”

The answer needs current market information

Use Application Expert and state that current data is required, or select QuantiQ Search for electronics pricing and availability. Include region, currency, quantities, and the date basis.

A part-number result looks wrong

Provide the manufacturer, full ordering code, and product family. Ask the assistant to disambiguate similar numbers before continuing and to cite the exact variant.

An attachment is not available to the assistant

Wait until processing completes, remove any failed attachment, and upload it again. Use a supported format and split unusually large or complex source sets into smaller groups if necessary.

A response appears stuck

Check the live service-status banner or Settings → About → Service Status. Keep the conversation open or return to it later; supported runs can finish in the background. Refresh only after allowing a complex request time to complete.

Mobile shows offline history

Reconnect to a stable network and pull to refresh. Use Settings → Refresh offline cache if needed. Verify that pending content has synchronized before closing or deleting anything.

The conversation has become confused

Summarize the confirmed facts and restate the current objective, or start a new chat with only the relevant files and requirements. A new chat is often best when the subject or assumptions have changed.

Recommended Working Pattern

For the most reliable results, use this sequence:

1. Start with Application Expert.
2. Define the decision or deliverable.
3. Provide the relevant context and files.
4. List hard requirements separately from preferences.
5. Specify source and freshness expectations.
6. Request citations, assumptions, and unknowns.
7. Refine through focused follow-ups.
8. Ask for the final output format.
9. Verify the answer and sources.
10. Give feedback and organize the chat.

When in doubt, ask Application Expert plainly: “Help me plan the best way to answer this, tell me what information is missing, and ask me the necessary questions before you begin.”