AIUNIFY PROS SUITE currently provides two closely related Sidebar areas covered in this chapter:
The Communication Tools are AI text-generation workspaces. The three items under Other are fundamentally different: Playground is the Website Builder's working editor, PPT Playground is the Presentation Studio editor, and Blank Template is currently a placeholder page intended as a foundation for custom features.
The current Sidebar deliberately separates:
Communication
from:
Other
The Communication category contains the three writing-oriented communication Tools, while Playground, PPT Playground, and Blank Template appear under the Sidebar category titled Other.
This chapter combines them because the stable AIUNIFY PROS SUITE manual architecture groups:
Communication Tools and Playgrounds
into one operational chapter.
However, subscribers should not assume all six work the same way.
The six entries use three distinct operating models.
The Sidebar item:
Playground
is not a generic Model-testing sandbox.
Similarly:
PPT Playground
is not a generic text Prompt playground.
It loads AIUNIFY's specialized:
PresentationDeck
workspace and is the editing/generation environment behind the Presentation workflow.
Blank Template is currently not an AI blank-prompt generator.
Its page describes itself as:
Blank Page Template
and:
Use this page as a foundation for custom features.
The active Communication Sidebar contains:
All three are currently marked:
New.
None of the three current Communication Sidebar entries is marked:
Pro
in the Sidebar definition.
Broader subscription and Tool-assignment rules can still apply.
| ToolRoute | |
| Apology Drafter | /apology-drafter |
| Negotiation Script | /negotiation-script |
| Elevator Pitch | /elevator-pitch |
The common workflow is:
Describe the Situation
→ Generate
→ Review Streaming Output
→ Copy or Download
→ Edit/Approve Externally
→ Deliver Through the Appropriate Communication Channel
Standard ToolPage requires an authenticated PROS SUITE session.
Unauthenticated users are redirected toward:
/login.
Each Communication Tool displays:
The shared left Card is:
Input
with:
Describe what you want to generate
There are no separate structured fields for:
Those details are entered within the Prompt.
Primary action:
Generate
The Standard workspace supports:
Ctrl + Enter
to begin generation.
If the Prompt is empty:
Input required
with:
Please enter a prompt to continue.
The response appears progressively in the Output Card.
Generated Communication content is rendered with AIUNIFY's standard Markdown renderer.
Standard ToolPage provides:
Copy
for completed Output.
The current confirmation is:
Copied!
Content copied to clipboard
Standard Communication Tools provide Download.
The current Standard download format is:
.txt
The Standard Output area is not directly editable.
There is no source-verified persistent Save function for these three Communication Tools.
There is no persistent history of previously generated:
through Standard ToolPage.
Reset clears the current:
and returns the workspace to its initial state.
The Communication Tools use AIUNIFY's shared generation architecture and therefore can use the subscriber's currently selected compatible AI Model.
Subscriber-configured AI provider API Keys can also use the shared Model/API-Key pathway documented earlier.
The individual page definitions provide:
The shared feature catalogue currently assigns:
20 Tokens
to all three Communication Tools.
| Communication ToolRoute FallbackFeature Catalogue | ||
| Apology Drafter | 10 | 20 |
| Negotiation Script | 20 | 20 |
| Elevator Pitch | 15 | 20 |
Standard ToolPage resolves Base Cost according to:
Live AI Limit → Feature Catalogue → Route Fallback
Therefore, absent a live override, the current effective Base Reference for all three is:
20 Tokens
Always use the Token Cost displayed in the live workspace if it differs from this manual.
Standard ToolPage can also apply its current OpenAI-provider display multiplier as documented earlier.
Navigate to:
Sidebar → Communication → Apology Drafter
Route:
/apology-drafter
Apology Drafter.
Current description:
Write sincere, effective apology messages — professional, personal, or customer-facing — with appropriate tone and follow-up actions.
Current guidance:
Describe the situation, who you're apologizing to, and the context...
Built-in example:
Write a professional apology email for missing a project deadline by 3 days
Built-in example:
Draft a customer service apology for a shipping delay on a premium order
Built-in example:
Create a sincere team-wide apology for a miscommunication that caused rework.
Tell the Tool who should receive the message.
Examples:
Give enough context to create a specific apology.
Explain how the event affected the recipient.
A customer-service apology can require different wording from a personal apology.
Examples:
If relevant, state whether the result will be used as:
The Tool description explicitly includes:
follow-up actions.
Provide actual corrective steps where known.
If no refund, replacement, credit, or corrective action has been approved, do not let the generated message promise one.
The message should identify what happened clearly.
A strong apology acknowledges why the event mattered.
Responsibility language should match the actual circumstances.
For disputes, legal claims, regulated situations, or unclear responsibility, generated language should receive appropriate review before delivery.
Where appropriate, state what is being done next.
Context can be useful, but excessive explanation can weaken the apology.
Examples:
provided those steps are real.
Apology Drafter creates text.
It does not send the message.
The generated apology is not automatically added to a customer record.
The Tool does not retrieve the affected customer automatically.
It does not retrieve support-ticket history.
An apology can mention a refund only as generated wording.
The Tool does not process money.
It does not determine whether wording creates or avoids legal liability.
There is no source-verified manager-approval process.
The workspace does not track whether the recipient opened or responded to the apology.
There is no persistent library of approved apology templates.
Do not allow AI to invent:
A minor delay and a serious operational failure require different tones.
Only promise deadlines or compensation that can actually be delivered.
High-stakes customer, employment, regulatory, or legal communications can warrant additional review.
Current filename:
apology-drafter-output.txt
Apology Drafter currently supports:
It does not establish:
Navigate to:
Sidebar → Communication → Negotiation Script
Route:
/negotiation-script
Negotiation Script.
Current description:
Create negotiation scripts with opening statements, key arguments, counterpoint handlers, BATNA analysis, and closing strategies.
Current guidance:
Describe the negotiation context — what you're negotiating, current offer, your target, and leverage points...
Built-in example:
Salary negotiation script: current offer $120K, target $140K, 5 years experience in cloud engineering
Built-in example:
Freelance rate negotiation: client offering $50/hr, I want $75/hr for a 6-month React project
Built-in example:
Vendor contract negotiation script to reduce annual SaaS licensing cost by 20%.
Identify what is being negotiated.
Examples:
The placeholder explicitly asks for the:
current offer.
Also provide the desired:
target.
The placeholder specifically requests:
leverage points.
Only provide legitimate facts.
Describe who you are negotiating with.
Negotiating with an employer differs from negotiating with a Vendor or prospect.
Include:
where relevant.
Explain realistic alternatives if the deal is not reached.
The Tool description specifically references:
BATNA analysis.
BATNA refers to the:
Best Alternative to a Negotiated Agreement
A Negotiation strategy is stronger when the subscriber understands what they will do if no agreement is reached.
Provide the real alternatives.
False statements about competing offers, approvals, or alternatives can create ethical, legal, or reputational problems.
The description explicitly supports:
opening statements.
The Tool can organize:
key arguments
around the subscriber's objectives.
The Tool description also includes:
counterpoint handlers.
The final supported concept is:
closing strategies.
For a stronger Script, ask for likely counterarguments.
Ask for concise responses to each expected objection.
You can ask the AI to organize:
as planning text.
The Tool generates a Script.
It does not conduct the negotiation with the counterparty.
It does not call an employer, Vendor, or Client.
It does not send the negotiation proposal.
The Tool does not alter a live Contract.
It does not verify whether a stated competing offer exists.
For salary negotiations, the current page does not source-verify live compensation databases.
For Vendor negotiations, it does not retrieve current competitor pricing automatically.
Contract negotiation can have legal implications.
Generated scripts do not replace appropriate legal review.
A well-written Script does not guarantee that the counterparty will agree.
Know the difference between the desired outcome and acceptable outcome.
Examples:
A Script should include how to respond if the initial request is rejected.
Do not use fabricated leverage.
Negotiation language can be assertive without becoming unnecessarily adversarial.
Employment, large contracts, and legal agreements can warrant professional review.
Current filename:
negotiation-script-output.txt
Negotiation Script currently supports:
It does not establish:
Navigate to:
Sidebar → Communication → Elevator Pitch
Route:
/elevator-pitch
The full page title is:
Elevator Pitch Generator.
Current description:
Craft concise, impactful elevator pitches in 30, 60, and 90-second versions with hooks, value props, and calls to action.
Current guidance:
Describe your product, service, or idea — what it does, who it's for, and what makes it unique...
Built-in example:
Create a 30-second elevator pitch for an AI-powered personal finance app targeting millennials
Built-in example:
Generate 3 pitch versions (30s, 60s, 90s) for a sustainable packaging startup
Built-in example:
Write a compelling elevator pitch for a job interview at a top tech company as a product manager.
Describe the:
The placeholder specifically asks:
who it's for.
Explain the problem solved or outcome provided.
The placeholder also specifically asks what makes the offering unique.
Request:
as appropriate.
The built-in Startup example demonstrates requesting all three duration versions in one Prompt.
Possible audiences include:
The Tool description explicitly includes:
calls to action.
The Tool description explicitly includes:
hooks.
Explain the pain or need where appropriate.
Introduce the Product, Service, or professional value.
The description explicitly references:
value props.
Explain why the offering is meaningfully different.
If you have real traction, credentials, or metrics, provide them.
Conclude with the desired next step.
Use for quick introductions.
Allows more context and differentiation.
Allows a more developed narrative.
The current Tool does not record the subscriber speaking and verify the actual duration.
Speaking pace varies.
Practice the final Script aloud.
The Tool generates Pitch text.
It does not assess:
It does not review:
The Tool does not send a Pitch to investors.
A Job Interview Pitch is not submitted to an employer.
Provide real:
rather than allowing the Model to invent proof points.
The workspace does not track:
A Pitch to a customer should differ from a Pitch to an investor.
Do not overload a short Pitch with too many problems.
Describe what changes for the audience.
Avoid generic phrases that could describe any company.
Examples:
The generated Pitch is a starting script.
Delivery affects impact.
Current filename:
elevator-pitch-output.txt
Elevator Pitch Generator currently supports:
It does not establish:
| CapabilityApologyNegotiationElevator Pitch | |||
| Standard ToolPage | Yes | Yes | Yes |
| Natural-Language Prompt | Yes | Yes | Yes |
| Examples | Yes | Yes | Yes |
| Streaming Output | Yes | Yes | Yes |
| Copy | Yes | Yes | Yes |
| TXT Download | Yes | Yes | Yes |
| Direct Edit | No | No | No |
| Save | No | No | No |
| History | No | No | No |
| External Sending | No | No | No |
| ActionCurrent Communication Tools | |
| Generate message/script | Yes |
| Copy message/script | Yes |
| Download TXT | Yes |
| Send Email | No |
| Make Phone Call | No |
| Negotiate With Counterparty | No |
| Publish Statement | No |
| Track Recipient Response | No |
| Process Compensation/Refund | No |
The current Sidebar category titled:
Other
contains:
The Sidebar helper explicitly excludes the category ID:
other
when calculating getAllSidebarTools().
This is an implementation distinction rather than a statement that its pages are unusable.
Within Other:
Navigate to:
Sidebar → Other → Playground
Route:
/playground
The /playground page renders:
PlayGround
inside a full-height Layout.
The underlying component is:
src/components/website/playground/playground.tsx
and contains:
The full Website Builder creation workflow is documented in:
Chapter 14 — Building Websites with Website Builder
Website project persistence, Preview, Save, and Publishing are documented in:
Chapter 15 — Managing, Previewing, and Publishing Website Projects
Chapter 46 documents Playground mainly as the Sidebar workspace entry and clarifies that it is not a generic sandbox.
Playground reads:
userprompt
from its URL parameters.
It also reads:
projectId
and can load a previously saved Website Project.
The Website Builder's Project page links:
+ New Project
to /playground.
Saved Website Project Cards link their:
Edit
action back into /playground?projectId=....
The Playground source explicitly deducts:
500 Tokens
before a new Website generation.
The deduction is associated with:
website-generation.
The generation request uses the subscriber's:
selectedModel.
If an Initial Image was supplied through the Website Builder entry workflow, it can be passed into the first Playground generation.
The internal generation Prompt instructs the AI to create responsive HTML using:
where appropriate.
The internal Prompt explicitly requests responsiveness across screen sizes.
The Prompt encourages:
Playground contains a dedicated:
ChatSection
alongside the Website Design area.
Each subsequent Website modification request deducts:
10 Tokens.
The AI is instructed to retain the existing design and return updated HTML when the subscriber requests changes.
Follow-up generation also uses the selected Model.
The Chat message structure supports an optional Image on a request.
Playground exposes:
Visual edits
inside the Chat interface.
The Playground maintains a selected:
for targeted editing.
When an element is selected, the AI is instructed to update only that specific HTML element and retain the surrounding Website.
Without a selected element, the broader Website Prompt is used to update the full existing design.
The targeted edit uses the same follow-up:
10-Token
deduction path as the normal SendMessage workflow.
Playground provides a persistent Website Save operation.
The save request stores:
and updates an existing Project if a projectId is present.
Successful save displays:
Website Saved Successfully!
When a new Project is saved, the URL can be updated to include its new Project ID.
Playground provides a:
Publish Website
dialog.
The subscriber enters a subdomain.
Current Input logic lowercases the value and allows:
a–z0–9If no value is supplied:
Please enter a subdomain
is shown before publication proceeds.
The button can display:
Publishing...
Current success message:
Website Published to Subdomain!
After a successful publish with a valid Project ID, the generated Site URL can open in a new browser tab.
Playground also provides an Unpublish pathway.
Success displays:
Website unpublished!
The shared feature catalogue includes:
Playground — 20 Tokens.
The specialized Playground's actual client code explicitly deducts:
For Playground operations, the explicit generation deductions are more relevant to subscribers than the generic catalogue's 20-Token reference.
Playground currently supports:
Its AI instructions and UI are designed around:
rather than arbitrary Model experimentation.
Navigate to:
Sidebar → Other → PPT Playground
Route:
/ppt-playground
The route explicitly checks the authenticated user and redirects unauthenticated users toward:
/login.
PPT Playground is wrapped in:
FeatureGuard featureId="ppt-playground".
The route renders:
PresentationDeck.
The full Presentation workflow is documented in:
Chapter 46 clarifies how the separate PPT Playground Sidebar entry relates to those workflows.
The Presentation Studio System Prompt requires:
exactly 8 presentation slides.
The architecture requests:
PPT Playground reads:
userprompt
from its search parameters.
It also reads:
projectId
to load an existing saved Presentation.
The Presentation Deck reads:
play=true
to initialize playback mode.
PPT Playground explicitly deducts:
500 Tokens
before generating a new Presentation.
The Token deduction identifies:
presentation-generation
as the feature.
A Design Chat edit explicitly deducts:
10 Tokens.
The same 10-Token Edit request can be used when a specific slide field has been selected.
The Presentation workspace streams generated Slide JSON and progressively merges parsed Slides into the Deck.
During generation, the UI creates eight temporary loading Slide objects.
As valid Slide objects arrive, they replace those placeholders.
If AI completely fails to produce parsed Slides, the current workspace can use pre-built fallback Slides.
Current message:
Using pre-built template slides for this topic.
The workspace maintains a message history for AI Presentation modifications.
A subscriber can request changes to the Deck through Design Chat.
The current AI edit Prompt explicitly instructs the Model not to rewrite Slides the subscriber did not request changes to.
Visual selection can identify a single field such as:
for targeted replacement.
The AI is instructed to return only the updated field value for a selected field.
The Presentation editing Prompt supports inline HTML style changes inside text-field values.
PresentationDeck maintains:
visualEditsActiveselectedFieldstate.
The workspace applies visual highlighting when Visual Edits is active.
This supports focused AI modifications rather than regenerating the entire Deck.
PPT Playground provides:
Save Presentation.
The save request stores:
The save routine derives the Project name from the first Slide's title.
Current message:
Presentation saved successfully!
PPT Playground therefore differs from Standard ToolPage: it supports saved Presentation projects.
The Presentation toolbar provides:
Export PPTX.
During export:
Exporting...
appears.
The Export action is disabled when the Deck contains zero Slides.
The full PPTX export mechanics are documented in Chapter 17.
The Presentation toolbar provides a:
Slide Grid View.
It also provides:
Toggle Fullscreen.
Saved Presentation Cards can launch the workspace with:
play=true.
Saved Presentation Cards also provide:
Edit
which routes to PPT Playground with the Presentation Project ID.
PPT Playground currently supports:
ppt-playground FeatureGuardThe workspace operates on AIUNIFY's current eight-Slide structured Presentation model.
It is not a general-purpose PowerPoint desktop replacement.
Navigate to:
Sidebar → Other → Blank Template
Route:
/blank
The Blank Template Route explicitly checks authentication and redirects unauthenticated users to:
/login.
The actual workspace heading is:
Blank Page Template.
Current description:
Use this page as a foundation for custom features.
The blank content area displays:
Start Building
Current text:
This is your blank canvas. Add your custom components and features here.
The visible page does not provide interactive controls for adding Components.
The plus-style icon is decorative in the current component.
There is no source-verified onClick handler.
Blank Template does not contain an AI Prompt field.
There is no AI generation operation.
The content area is a dashed placeholder region rather than a working visual builder.
Subscribers cannot select custom Components from a palette.
There is no subscriber Save action in the current BlankPage component.
There is no Publish action.
There is no Download or Export.
The source wording:
Use this page as a foundation for custom features
and the source comment:
Content Area - Ready for Customization
indicate that this page is currently a template/foundation rather than a completed subscriber creation Tool.
The shared catalogue includes:
Blank Template — 20 Tokens.
The current BlankPage component contains no:
Therefore:
Do not describe 20 Tokens as an actual Blank Template usage charge based on the present subscriber implementation.
The catalogue value exists, but the actual visible page is currently a static placeholder.
Blank Template currently supports:
It does not establish:
| CapabilityPlaygroundPPT PlaygroundBlank Template | |||
| Specialized Workspace | Yes | Yes | No |
| AI Generation | Yes | Yes | No |
| Persistent Projects | Yes | Yes | No |
| Visual Editing | Yes | Yes | No |
| Chat Editing | Yes | Yes | No |
| Save | Yes | Yes | No |
| Publish | Website | No direct web publish | No |
| Export | Website/code workflow | PPTX | No |
| Initial AI Cost | 500 | 500 | No source-verified charge |
| AI Edit Cost | 10 | 10 | N/A |
Apology, Negotiation, and Elevator Pitch do not provide persistent projects.
Website Playground supports saved Website Projects.
PPT Playground supports saved Presentation Projects.
There is no content-entry workflow to persist.
Decide whether the purpose is:
Give the AI the actual situation.
Use the appropriate Communication Tool.
Check:
Standard ToolPage has no direct Output editor.
Use the appropriate:
system.
The Communication generators do not measure real-world response.
Website Builder Prompt
→ Playground
→ Generate Site
→ Review Preview
→ Chat/Visual Edits
→ Save
→ Publish
→ Maintain Saved Project
Pitch Deck Prompt
→ PPT Playground
→ Generate 8 Slides
→ Review
→ Design Chat/Visual Edits
→ Save
→ Export PPTX or Play
Current workflow:
Open Blank Template
→ View Placeholder
There is no source-verified subscriber construction workflow beyond that in the current implementation.
Provide:
Remove the promise or regenerate using only approved remediation.
Apology Drafter generates text only.
Use the appropriate Communication system.
No persistent template library exists in this Tool.
Preserve it externally.
Provide:
Verify external compensation, Vendor, or pricing data separately.
Negotiation Script produces preparation text only.
Use an appropriate document/legal workflow.
Specify the desired:
30-, 60-, or 90-second
version.
Provide:
Replace them with real verified facts.
The current Tool does not analyze spoken delivery.
Playground can be entered without a userprompt.
For a normal creation flow, begin from Website Builder or provide the appropriate Website Prompt.
The Website generator attempts to deduct:
500 Tokens
before initial creation.
Follow-up AI Website edits require the source-defined:
10 Tokens
per request.
The current error can be:
AI did not generate any code.
A follow-up modification can report:
AI did not generate any valid code for this modification.
The current save path reports a server-provided error or:
Error saving website
when necessary.
Enter a valid subdomain first.
Review the error message returned by the Publishing operation.
Enable:
Visual edits
and select the relevant element before sending the targeted request.
The route is protected by:
FeatureGuard featureId="ppt-playground"
in addition to authentication.
The Presentation generator deducts:
500 Tokens.
Follow-up AI edits deduct:
10 Tokens.
The current workspace can fall back to pre-built Slides and display:
Using pre-built template slides for this topic.
At least one Slide must exist and no export can already be in progress.
The Save button is disabled while saving or when there are no Slides.
The current Blank Template does not provide one.
The plus graphic is part of the placeholder presentation.
The current source does not assign it an action.
There is no current component-addition interface.
No Save operation is implemented.
The page is currently positioned as a:
foundation for custom features
rather than a completed subscriber builder.
Communication text can directly affect relationships and business outcomes.
Check factual claims.
Especially check:
Do not accidentally create commitments the organization has not approved.
Legal, employment, or financially significant negotiations can require professional review.
Do not unnecessarily include:
in Communication Prompts.
Apology Drafter
→ Review
→ Copy
→ Email System
→ Send
There is no automatic handoff.
Negotiation Script
→ Review
→ Practice
→ Use in Meeting/Call
The Tool does not participate in the live negotiation.
Elevator Pitch Generator
→ Approve Pitch
→ Pitch Deck/PPT Playground
→ Build supporting Slides
No automatic transfer is source-verified.
Unlike Standard Communication Tools, Website Playground does provide a direct source-verified Publish workflow.
Unlike Standard Communication Tools, PPT Playground provides direct source-verified PPTX export.
| ToolEffective Current Base Reference* | |
| Apology Drafter | 20 |
| Negotiation Script | 20 |
| Elevator Pitch | 20 |
*Absent a live AI-limit override; Standard ToolPage catalogue precedence applies.
| ActionSource-Verified Deduction | |
| Initial Website Generation | 500 Tokens |
| AI Modification | 10 Tokens |
| ActionSource-Verified Deduction | |
| Initial Presentation Generation | 500 Tokens |
| AI Edit | 10 Tokens |
Although the shared feature catalogue contains a 20-Token Blank Template entry, the current page has no AI operation or source-verified Token deduction.
All three Communication Tools support:
None of the three provides:
Both are specialized AI creation/editing environments with:
Website Playground creates and publishes Website Code.
PPT Playground creates and exports structured Presentations.
Blank Template currently contains neither of those AI-generation/editing engines.
AIUNIFY PROS SUITE currently provides three active Communication Tools:
All three are marked New and use Standard ToolPage.
Apology Drafter is designed to create:
and includes built-in scenarios involving a Project Deadline, Shipping Delay, and Team Miscommunication.
It creates the message but does not send it, process remediation, or track the recipient's response.
Negotiation Script generates preparation material containing:
with current examples for Salary, Freelance Rate, and Vendor Contract negotiations.
It prepares the subscriber for a negotiation but does not negotiate, modify a Contract, call the counterparty, or validate market data automatically.
Elevator Pitch Generator is designed to create:
Pitches with Hooks, Value Propositions, and Calls to Action.
It generates Pitch text but does not record, time, coach, submit, or measure delivery.
The Communication page Routes contain:
while the shared feature catalogue assigns:
20 Tokens to all three.
Because Standard ToolPage gives the feature catalogue higher priority than the Route fallback, the current default Base Reference is 20 Tokens for each absent a live override.
The current Other Sidebar contains:
These should not be treated as three generic AI sandboxes.
Playground is AIUNIFY's specialized Website Builder editing environment.
The source verifies:
Its complete Website-building operation is covered in Chapters 14 and 15.
PPT Playground is the specialized Presentation Studio.
The current source verifies:
ppt-playground FeatureGuardIts complete Presentation operation is covered in Chapters 16 and 17.
Blank Template currently opens a page titled:
Blank Page Template
with the messages:
Use this page as a foundation for custom features
and:
This is your blank canvas. Add your custom components and features here.
However, the current subscriber source does not provide interactive component creation, AI Prompting, Save, Publish, or Export functions on that page.
It should therefore be documented as a current placeholder/template foundation—not as a finished no-code builder.
The central operating principle for Chapter 46 is:
AIUNIFY PROS SUITE Communication Tools generate text that helps subscribers prepare what to say; they do not deliver the communication or perform the real-world negotiation. The Sidebar Playgrounds are different: Playground and PPT Playground are specialized, persistent Website and Presentation creation environments with real Save and editing workflows, while Blank Template is currently only a foundation/placeholder page rather than an operational AI builder.