Assistant And Project Workspace

Nilo's core working surface is a persistent assistant workspace. Conversations are saved, searchable, and can be grouped by project so the business can keep ongoing work in context instead of treating every request as a separate one-off prompt.

Inside a conversation, users can attach files, record voice input, keep generated artifacts, and work from a project item or business context that stays connected to the thread. The result is closer to an ongoing work area than a disposable chatbot window.

• What it is: saved conversations, project grouping, attachments, voice input, artifacts, and shared or private chat visibility.
• What it does: turns rough notes, documents, and ongoing requests into reusable working context for the business.
• Typical use: proposal drafts, internal notes, file-based work, and ongoing project work that needs to stay in context.

Communication, Drafting, And Follow-Up

The communication area is a mailbox workflow inside Nilo rather than a simple drafting add-on. A user can connect a mailbox, work from inbox and sent mail, search messages, review summaries, and move directly from a message to a drafted reply or a new composed message.

Nilo also supports follow-up work around that communication. The business can turn chats or message context into reminders so promised callbacks, deadlines, and next steps are less likely to disappear into the day.

• What it is: mailbox connection, inbox and sent views, search, summaries, compose, reply drafting, and follow-up reminders tied to business context.
• What it does: keeps customer communication, written follow-up, and promised next actions in one place.
• Typical use: email drafting, reply cleanup, reminder setting, and day-to-day customer communication.

Contacts And Relationship Memory

Nilo includes a contact layer that keeps people, companies, communication history, and business notes tied together. Contacts can be added directly, discovered from communication, and enriched over time as more work happens in the system.

The contact detail view is designed to hold the running memory around a relationship: communication history, AI-written summaries, related people from the same business, preferred language, and other context that helps later replies and follow-up stay informed.

• What it is: contact records, discovered contacts, communication history, rolling summaries, related contacts, and client-specific notes.
• What it does: helps the business remember who people are, what has been discussed, and how the relationship has developed.
• Typical use: keeping track of customers, suppliers, repeat contacts, and relationship history over time.

Website Publishing And Website Widgets

Nilo includes a website area for businesses that want the website kept inside the same product rather than handled as a completely separate system. The current workflow supports uploading and publishing static site versions, reviewing deployment history, rolling back to an earlier version when needed, and managing widget snippets from one setup surface.

The website area now includes current embeddable widgets such as:

• Contact form: for inquiries and contact capture.
• Chatbot: for automated website replies.
• News feed: for short updates and announcements.

More widgets are in development, and partners can also request new ones based on client needs. That keeps website publishing and website interaction inside the same operating setup instead of splitting it across separate tools.

• What it is: website publishing, deployment history, rollback, shared widget setup, and embeddable contact form, chatbot, and news feed widgets.
• What it does: keeps the business website, customer inquiries, automated website replies, and simple website updates inside the same operating setup as the rest of the work.
• Typical use: website refreshes, site publishing, rollback, contact capture, website Q&A, and posting short updates or announcements.

Version history: the website workflow keeps upload history so earlier versions remain available as rollback points when a change needs to be undone.

Content Studio For Images

Image work lives inside Content Studio as a saved, project-based workflow. Instead of generating one image and losing the context, the business can keep image threads, come back to earlier work, and organize visual tasks by project.

The current image workflow already supports practical controls such as aspect ratio, resolution, framing, and style. It also supports reusable reference subjects so recurring people, products, or brand elements can stay more consistent across later image work.

• What it is: saved image threads, project-based organization, image controls, and reusable reference subjects.
• What it does: creates campaign visuals, proposal support images, and repeatable brand imagery without leaving the main product workflow.
• Typical use: promotional images, concept images, and recurring visual assets for the business.

Video Chat

Video chat is part of Content Studio. It keeps video prompts, outputs, and related context together in the same thread-based workflow used for other studio work.

The main use is short promotional clips, concept videos, and other visual outputs that need motion rather than still images.

• What it is: video prompt threads inside Content Studio for short AI-generated videos.
• What it does: creates short videos while keeping prompts and outputs together in the same working context.
• Typical use: short promo videos, concept clips, and other motion-based visual material.