This chapter brings together the recommended operating practices for using AIUNIFY PROS SUITE efficiently, accurately, securely, and consistently.
The PROS SUITE contains many different types of Tools, including:
Although these Tools operate inside the same PROS SUITE environment, they do not all behave identically.
The most important operating principle is:
Understand the Tool you are using, provide it with accurate information, review what it produces, preserve important work, and never assume that a feature exists across every Tool simply because another Tool provides it.
Before starting an important task, determine whether the Tool is:
Different Tool types have different:
For example:
Website Builder can save projects.
Pitch Deck can save presentations.
Game Developer can save games.
Image Generator maintains Generation History.
Video Generator maintains a Video Gallery.
Standard ToolPage generators do not provide universal Save or History.
A Standard ToolPage generally provides:
Specialized Tools can contain their own:
Use the instructions for that specific Tool rather than assuming Standard ToolPage behavior.
The Tools available to a subscriber can depend on:
If another subscriber can see a Tool and you cannot, first consider whether:
Use the Sidebar to determine which Tools are currently available through your account.
A previously saved Tool URL does not guarantee that the Tool remains available under the subscriber's current Plan or permissions.
Before beginning several large generations, review your available Token balance.
Standard ToolPage displays:
[X] tokens per use
and:
Your balance: [X] tokens.
Do not regenerate simply because the first response requires a small correction.
When possible:
A poorly prepared Prompt can produce an unusable result and require additional generation.
Write the important requirements before selecting Generate.
If the Tool needs:
include those details before generating.
Different Tools can use different Token amounts.
Token cost is Tool-specific.
For Standard ToolPage, the displayed base cost can come from the system's configured AI limits, the Tool's feature definition, or its route fallback.
The selected provider can also affect the displayed amount; the current Standard ToolPage applies a 1.5× display multiplier when the selected model provider is OpenAI.
The Header contains the current Model selection interface.
The selected Model is displayed by name and can be changed where permitted.
Select a Model because it supports the current objective, not simply because more options are available.
When consistency matters, use the same Model throughout related:
unless you intentionally want different behavior.
Different Models may vary in:
Some Models may depend on an available Provider configuration or subscriber API Key.
The subscriber Settings interface includes:
API Keys
and:
Security (2FA)
where those capabilities are enabled.
Do not use:
Do not paste API Keys into:
Subscriber provider keys are used by supported AI requests through provider-specific request headers when configured.
The system has a dedicated API-Key mechanism.
Prompt text is not the appropriate location for credentials.
Make sure the Key corresponds to the Provider you intend to use.
If you believe an API Key has been exposed:
Use a unique Password that is not shared with unrelated services.
Your email can be involved in:
Protecting that email account helps protect PROS SUITE access.
PROS SUITE contains subscriber 2FA functionality and maintains whether 2FA is enabled on the account.
Keep Recovery Codes in a secure location separate from your normal login credentials.
Do not send:
through unprotected communication channels.
Do not leave an authenticated PROS SUITE session open on a device you do not control.
A strong Prompt tells the AI:
Instead of:
Write marketing copy
use:
Write a 150-word landing-page hero section for a B2B accounting platform targeting accounting firms with 10–50 employees. Emphasize automation, client management, and time savings.
AI output improves when the Tool understands the situation.
Useful context can include:
Identify whether the content is for:
Examples:
Ask for the result in the form you actually need.
Examples:
Examples:
Useful constraints include:
If exact business information matters, provide it.
Do not expect the AI to know private or organization-specific facts that were never supplied.
Many Standard ToolPages include example Prompts.
They demonstrate how the Tool can be used.
Do not blindly submit an example Prompt when your real situation is different.
Replace example details with:
Generated content should be reviewed before it is:
Confirm:
are named correctly.
Check:
Do not publish a factual claim only because the AI generated it.
If generated content contains URLs or references, confirm they are correct before publication.
Make sure the generated content reflects the intended:
Check:
before final use.
A generated answer and an externally verified fact are not the same thing.
Legal-document Tools can assist in drafting.
Important legal documents should receive appropriate legal review before reliance or execution.
Financial-analysis and Finance Helper outputs should be reviewed against actual financial records.
Health-related Tool output should not replace appropriate professional evaluation where one is required.
AI Analysis and trading Signals should not be treated as guaranteed market outcomes.
Use independent risk management and decision-making.
Generated Code should be:
before production use.
Standard ToolPage's current user interface provides Copy and Download but no universal project Save or History.
Use Copy when you need to move the result into another:
Standard ToolPage downloads the generated result as a .txt file.
Reset clears the Standard ToolPage workspace state.
Unless the specific Tool contains History or Save, preserve the output first.
Use the Website Builder Save operation before leaving important Website work.
Wait for the success confirmation before assuming the project has been preserved.
When working from a saved Website Project ID, Save updates that existing project rather than necessarily creating a new one.
A saved Website project and a published Website are different states.
Save important Presentation work before leaving the Pitch Deck workspace.
Pitch Deck uses the first Slide Title when naming the saved Presentation.
Choose a useful Title before saving.
Select:
Save Game
when you need the generated Game to remain available inside Saved Games.
Downloading a Website, Presentation export, Game, or generated file does not necessarily create or update an internal saved project.
For business-critical work, maintain external copies where appropriate.
Consider preserving downloadable Website source for important final versions.
Export important final Presentations to PowerPoint.
Download important finished Games as HTML.
Download approved final:
Download or copy final:
Different PROS SUITE Tools have different persistence mechanisms.
Uses:
Generation History.
Uses:
Video Gallery.
Uses:
Generation History.
Uses:
Your Work.
Uses:
Your Archive.
Uses:
Your Thumbnails.
Use:
Design History.
Uses:
Saved Games.
Uses:
Your Saved Presentations.
Uses its own saved Website Project collection.
AI Marketing Studio's Recent Assets section filters the returned asset collection to Images and Videos and displays up to eight entries.
For older or specialized Marketing assets, open the corresponding Tool.
Once an asset is approved, download the final version.
For valuable brand assets, preserve the Prompt used to create the asset.
This makes future variations easier.
Some Design histories allow an existing asset to be returned to the active workspace.
Use that workflow rather than rebuilding from memory.
Avatars can be reused across supported Marketing workflows.
Meaningful names make future selection easier.
Verify that the intended Avatar is visibly selected before submitting the generation.
Reuse an existing Avatar when it already represents the desired subject.
User-created Avatars can support Delete where allowed, and the current Delete confirmation warns that the action cannot be undone.
When uploading a Product Reference, use an Image where the intended Product is clearly visible.
The ProductPicker derives the Product name from the uploaded filename.
Use meaningful filenames before upload.
Instead of:
IMG_4873.png
prefer:
Premium-CRM-Dashboard.png
when appropriate.
Confirm the selected Product Reference visually before submitting.
ProductPicker loads previously uploaded Products for reuse.
Specify what should appear in the Image.
Include:
when relevant.
Examples:
Choose the format based on the final use.
Check for:
After a successful Image creation, confirm it appears in Generation History before relying on it as persisted work.
Video generation depends heavily on movement instructions.
Examples:
A short generation should not be expected to perform too many unrelated actions.
Choose the format appropriate to the intended destination.
Do not judge only the first frame.
Keep an external copy of the version you intend to use.
Include:
when relevant.
Normal Mode is useful for simpler generation.
Custom Mode provides additional creative inputs.
A meaningful Title helps identify tracks in Generation History.
Music Generator provides:
Refresh History
for reloading prior creations.
Keep an external copy when a generated track will be used in production.
Include:
A complete first Prompt reduces the number of corrective edits.
Review the generated Website visually.
Verify:
Review the site at different browser widths before publication.
Save a useful Website state before making substantial revisions.
Ensure the current version is preserved before publishing.
After Publish, open the published Website and inspect the live result.
Unpublishing removes the publishing state but is separate from deleting the saved Website project.
Specify whether the deck is for:
Examples:
For investment and business presentations, supply verified figures rather than expecting the AI to invent them.
Check:
Preserve the internal Presentation project before creating the external PowerPoint.
After final review, export the version intended for distribution.
Include:
Use the Preview before saving.
Use:
Save Game
for PROS SUITE persistence.
Keep the standalone .html file if the Game is important.
The current Save Game workflow preserves core values including Code, Prompt, Genre, and Visual Style rather than every generation configuration.
Tell the Tool whether the writing should be:
Writing for an executive should differ from writing for a consumer or student.
Even polished AI output should be reviewed before publication.
For non-persistent generators, use Copy or Download.
Content intended for LinkedIn should not automatically be used unchanged on Instagram or X.
Tell the Tool who the post should reach.
Generated hashtags should be reviewed for relevance before publishing.
Most content-generation Tools create copy.
Generation is not automatically social-media publication unless the specific Tool contains a verified connection/publishing workflow.
For example, Instagram Caption Generator and Instagram Auto-Reply Agent perform different functions.
A strong Marketing workflow begins with a clear:
If the Persona is generated without real customer data, treat inferred attributes as hypotheses to validate.
Competitor Analysis should be supplied with current known information when accuracy matters.
The current Standard ToolPage path does not establish live Internet research for that generator.
When creating Pricing Page Copy, provide the correct:
It generates variants.
Use an appropriate delivery or analytics environment to conduct and measure the actual test.
Google Ads and Facebook Ads generators create copy.
They do not, by themselves, establish campaign deployment.
Business plans and analysis are more useful when based on real:
Check user-entered figures before relying on AI-generated financial guidance.
A generated:
is content.
It does not automatically execute the underlying business process.
Clearly identify:
where relevant.
For debugging work, provide the exact:
when appropriate.
Include enough surrounding Code to understand the problem.
Remove:
before pasting Code.
Generated Code should not be moved directly into production without validation.
For important software work, preserve tested Code in the organization's normal source-control workflow.
State whether material is for:
Specify what the learner should know or be able to do.
Review generated instructional material for factual accuracy.
AI-generated:
should be adjusted to the real learner or curriculum when appropriate.
Specify:
Use generated concepts as starting points where further creative development is needed.
If a creative result is worth keeping and the Tool has no History, copy or download it immediately.
Legal requirements can differ by location.
If the Tool needs jurisdictional context, provide it.
A Privacy Policy is only useful when it reflects how the business actually handles information.
Review generated legal documents before use.
For important agreements, regulatory matters, or legal obligations, use appropriate professional legal review.
SEO content should reflect the actual page.
Do not force unrelated keywords simply because the Tool can generate them.
Confirm generated Titles and Descriptions:
Generated Schema Markup should be checked before adding it to a production Website.
Generated SEO recommendations should be treated as optimization assistance rather than guaranteed search-engine performance.
AI cannot reliably correct every underlying data-quality problem automatically.
When analyzing unfamiliar data, provide context for important fields.
Compare important calculations to the original dataset.
A chart value and an AI interpretation of the value are different things.
If required information is absent, identify the gap instead of treating an estimate as a measured fact.
The Portfolio workflow documented in Trading Terminal is a simulated/Paper Portfolio environment rather than a source-verified live broker execution system.
BUY, SELL, or HOLD signals are analytical output.
They are not guaranteed future outcomes.
Consider:
before making an independent decision.
For time-sensitive decisions, independently confirm live market conditions.
Use independent judgment and appropriate risk management.
Browser Control works better with a specific objective.
Instead of asking it to investigate an entire industry without boundaries, define:
Do not assume the final AI synthesis captures every detail correctly.
Copy or download the final synthesis when needed.
Make sure the intended Input device is available.
Verify Video state before joining or hosting.
Meaningful meeting Titles make activity easier to understand.
The source-verified meeting functionality documented earlier does not establish automatic Meeting Recording as a subscriber feature.
If information must be preserved, use only the persistence/export mechanisms actually available in the meeting workflow.
Use relevant business information rather than uploading unrelated documents.
Replace outdated information with current information when the business changes.
Use the available testing workflow before embedding the Agent on a live Website.
Examples should include:
Make sure the Agent correctly reflects the supplied Knowledge Base.
Know whether the Agent is expected to:
according to the functions actually configured.
The more precise the Agent's operating instructions, the easier its behavior is to evaluate.
Use controlled scenarios before using any automated Agent in important customer interactions.
Before enabling automated replies, confirm the intended account is connected.
Provide clear:
Run representative conversations before relying on automation.
Automation should not eliminate appropriate business oversight.
When a Tool specifies accepted formats, use those formats.
Some Tools enforce specific upload sizes.
Review the filename before submitting.
Do not upload confidential information simply because a Tool allows a document or image.
Not every uploaded file becomes part of a reusable PROS SUITE Asset library.
Downloaded files are normally handled by your browser and operating system.
Generated filenames may be generic.
Rename important files after download if necessary.
Maintain an external organizational structure for important:
Open important downloaded files and confirm they are usable.
Do not select Delete merely to remove something from the screen temporarily.
Website Projects, Presentations, Games, and supported Avatar deletion workflows contain destructive confirmations.
Download or otherwise preserve anything that may be needed later.
The current source does not establish a universal subscriber Recycle Bin.
A few additional seconds of Prompt preparation can prevent several unnecessary generations.
For complex work, build the Prompt from:
Objective + Context + Audience + Required Information + Constraints + Output Format
Objective: Create a sales email.
Context: We sell a CRM platform to independent insurance agencies.
Audience: Agency owners with 10–50 producers.
Required Information: Lead management, automation, reporting.
Tone: Professional and concise.
Output: Subject line plus a 150-word email with one CTA.
Ask whether the problem can be fixed by changing only a small portion manually.
When refining output, changing one major instruction at a time makes it easier to understand what improved the result.
PROS SUITE is most effective when Tools are combined into repeatable workflows.
Buyer Persona
→ Competitor Analysis using verified information
→ Marketing Plan
→ Landing Page Copy
→ Ad Copy
→ Email Copy
→ Social Content
→ Creative Assets
→ Review
→ Download/Deploy
Business Requirements
→ Website Builder
→ Preview
→ Edit
→ Save
→ Review
→ Publish
→ Verify Live Site
→ Preserve External Copy
Define Objective
→ Generate Pitch Deck
→ Review Slides
→ Refine Design
→ Save Presentation
→ Play/Test
→ Export PowerPoint
→ Final Review
Research/Source Information
→ Writer
→ Grammar Check
→ Content Improver
→ SEO Tool
→ Final Human Review
→ Download/Publish
Before using generated work externally, review:
The AI generates.
The subscriber approves.
Once a result is finalized, preserve a clearly identified approved copy.
When working in project-based Tools, understand whether Save updates an existing Project ID.
Do not summarize an error too quickly.
The exact message can indicate whether the issue involves:
Before repeatedly selecting Generate:
Do not repeatedly regenerate the same Prompt if the underlying issue has not changed.
If a Tool unexpectedly redirects to Sign In, verify the account session.
If a Tool is unavailable, review the subscriber Plan and assigned Tool access.
If one Model fails, confirm its Provider/API requirements before assuming the Tool itself is broken.
Provide only the information necessary for the task.
Never include:
in ordinary generation prompts.
Before uploading a document, verify it does not contain unnecessary confidential material.
Where a company has established:
procedures, follow them when using AI-generated content.
Use generated financial information as assistance, not an unquestioned final authority.
Use generated legal drafts as documents requiring appropriate review.
Use health-related outputs cautiously and seek appropriate professional evaluation where required.
Do not interpret generated market analysis as guaranteed performance.
Do not deploy generated Code without testing.
Recommended routine:
Confirm:
Confirm:
Determine whether you need to:
depending on the Tool.
For important work:
Do not provide minimal information for a complex task and then expect a precise result.
Do not repeatedly select Generate without changing the Prompt or correcting the problem.
Generation is not independent fact-checking.
Standard ToolPage does not provide universal History.
They are different operations.
Especially in Website Builder.
Marketing asset histories differ by Tool.
Specialized generators may use their own AI or media-generation infrastructure.
Never place sensitive credentials in ordinary Tool inputs.
AI output should be reviewed before public or business use.
Know what you are trying to accomplish.
Choose based on function rather than convenience.
Gather the information needed before generating.
Know the resource requirement and current AI configuration.
Submit a complete Prompt.
Check the result for accuracy and usefulness.
Improve the result through editing or additional instructions.
Use the Tool's appropriate:
operation.
Move approved content into the business process where it belongs.
Check the final:
after implementation.
Do not force one generator to perform a task better suited to another specialized PROS SUITE Tool.
AI quality depends heavily on Input quality.
Know what the Tool creates and what it does not execute.
Generated content should be checked before important use.
Know whether the Tool uses:
Use generation resources intentionally.
Use Security Settings and protect API Keys appropriately.
Use external file organization for approved business deliverables where appropriate.
The greatest operational value comes from combining specialized Tools into predictable business processes.
AIUNIFY PROS SUITE contains both shared generator interfaces and deeply specialized workspaces.
Do not assume that:
works identically across every Tool.
A complete Prompt should normally establish:
Objective + Context + Audience + Facts + Constraints + Desired Output
This improves usefulness while reducing unnecessary regeneration.
Standard ToolPage displays both the current Token Cost and subscriber Token Balance, allowing the subscriber to review resource use before generating.
The PROS SUITE Header exposes the currently selected Model and available Model-selection workflow where configured.
Use Model changes intentionally rather than randomly.
Settings provides API-Key and Security controls where enabled, and supported AI requests can send subscriber-configured provider keys through provider-specific request headers.
Treat those Keys as credentials.
Standard ToolPage provides Copy and Download but does not establish universal Save or History.
Specialized Tools can instead provide:
These actions are not interchangeable.
Save generally preserves supported internal project state.
Download creates an external file.
Export converts content into another deliverable format.
Publish makes supported content available through a publishing workflow.
Before important use, review:
The AI generation process should not be treated as independent verification.
For important business operations:
AI generates and assists. The subscriber reviews, validates, approves, and decides how the result is used.
For important work, use both:
This is particularly important for:
The PROS SUITE is most effective when subscribers move deliberately from:
Plan → Generate → Review → Refine → Save → Export → Execute → Verify
rather than treating every Tool as an isolated one-time generator.
The complete operating standard for AIUNIFY PROS SUITE can be summarized as:
Select the correct Tool. Configure the correct Model. Understand the Token cost. Provide accurate and complete information. Generate with a clear objective. Review every important result. Verify factual or high-impact content independently. Protect account credentials and API Keys. Save projects where Save is supported. Download or export important final deliverables. Understand the difference between temporary output, persistent projects, asset history, and publication. Use specialized Tools according to their actual capabilities, and build repeatable workflows that move AI-generated work into measurable business execution.
Chapters 1–49 Complete
This concludes the primary AIUNIFY PROS SUITE User Operations Manual, covering subscriber operation from initial account access and security through Tool navigation, AI generation, specialized business workflows, project and asset management, troubleshooting, and recommended operating practices.