--- version: 2026-10-22.3 updated: 2026-10-22 lang: en canonical: https://azothops.com/en/brand/guida-contenuti title: Tell the AzothOps story with care. description: The public reference for creating content with ChatGPT and other AI tools: the idea, tone, examples and limits of what we promise. historical_background_version: 2026-09-25.1 --- ## Social: what I build and how I work Social model updated on 22 October 2026, version 2026-10-22.3. The sections below retain the 25 September 2026 background reference; their historical availability statements are not current operational status. For current product and contact availability, consult the current public pages and the Italian Markdown guide. This update does not activate features, publishing, messaging or permissions. The purpose of a post is to help a relevant business learn a practical customer-assistance improvement and understand the work behind AzothOps. Show what I build, test or study, how it works, the concrete benefit for the business and its customer, and a useful takeaway. The post must help even someone who neither buys nor comments. Interested businesses can then assess the work and start an informed conversation. Write the founder's account in first-person English. Use one recognisable customer situation, the facts that affect the decision, and the retrieval, clarification, preparation or handoff being designed or used. Connect the action to a prepared team, less repetition, a clearer decision or a customer who can continue. Do not accuse the viewer, invent numbers, clients or outcomes, or turn a proposed design into a completed result. Claims such as “I built”, “I test” and “I use” need evidence; otherwise say “I am designing”, “I am developing” or clearly mark an illustrative example. Each post needs its own useful idea, not the same opening repeated. Assign every element a purpose: a hook identifies a relevant situation; the first-person account shows the work; an example makes it understandable; the useful action explains the method; the benefit makes it relevant to the buyer; and the resource supports a practical next step. Desire comes from observable usefulness. Omit detail that does not help someone understand, apply or assess the work. Each caption starts with COMMENT "KEYWORD", using a relevant uppercase keyword, then a blank line and the useful description. In a video, say the matching comment request once at the end, after delivering the useful explanation. Prepare the actual matching resource and manual reply before scheduling. Do not claim a resource was sent or promise automatic delivery when that path is not enabled and verified. For the current visual comparison, A uses a relevant full-frame photographic or illustrated scene with readable words and subtitles; B uses plain text cards. Both are narrated MP4 videos with quiet original instrumental music. A matched visual comparison keeps the words, voice, music and timing the same and changes only the visual treatment. Voices and music may rotate between comparisons; unpaired organic posts do not establish causal preference. Use the AzothOps Meta app for the native calendar. Remove overlapping legacy placements only after verifying their replacements. Prioritise relevant resource requests, useful business conversations and observed use of the material when known. Available views, saves and shares are secondary observations. A comment is not automatically a qualified lead; unsupported or unobserved outcomes remain unknown. ## Start with the person AzothOps speaks to businesses that want to care for their customers. Someone asks for help, wants to feel heard and needs to know what they can do next. Start the content with that everyday situation, in plain language. The idea to communicate: help businesses provide useful, thoughtful answers using approved information, with a person involved when needed. A good answer can save the customer another problem before they need to ask. Describe this care without accusing businesses of neglecting customers or losing sales. The shared aim is to help people feel looked after by the business they trust. ## What we can say about AzothOps AzothOps already has a developed product that is being tested. Its commercial introduction lets people explore the service and assess a suitable configuration; it is not a fundraising campaign to build the product. The voice and text assistant uses a knowledge base dedicated to the business. The RAG system looks for relevant information in the available sources; the team checks those sources, approves updates and decides when to involve a person. Procedures, languages, channels and connections need configuration and testing for each business. Public examples are illustrative. Recorded AI voices are not live conversations, nor do they demonstrate that every integration or language is ready for every business. This page is a public editorial guide for creating content. It does not configure an assistant, add knowledge to an operational RAG system or replace a client business’s approved information. ## A direct answer, plus a useful detail Show a simple sequence: - Answer the question using confirmed information. - Add a relevant detail that helps the customer with their next step. - Involve a person when information is missing or a decision is needed. Illustrative example: “Are you open on Saturday morning?” Answer: “Yes, from 9 am to 1 pm. When you visit, you can use our private car park.” Parking information helps someone plan a visit. Mention it only if the car park exists, is available to that customer and has been confirmed by the business. The opening hours and parking in this example are fictional; they do not automatically apply to every business. There is no need to make every answer longer. The detail must be verified and useful in that context. Otherwise, a short, accurate answer is better. ## At the garage: when the car is actually ready Illustrative example: “Can I collect the car at 4 pm?” If the garage has confirmed that the car will be ready for collection at 4 pm: “Yes, you can collect it at 4 pm.” A practical, verified detail can be added if it helps with collection. If readiness is not confirmed: “The collection time has not been confirmed yet. It needs to be checked with the garage.” Do not invent a time, a callback or an action already taken. Say a request has been passed on only when that handover is supported and has actually happened. “I’ll update you by 4 pm” is a different commitment: it does not mean the car will be ready at 4 pm. It can only be offered when authorised; it should not be presented as AzothOps’s distinctive value or as proof that the problem is solved. The care we describe helps customers make plans based on what is true. ## Tone, format and identity Write clearly, warmly and concretely. Use readable sentences, a recognisable situation and a practical benefit. AI is the tool; customer care is the message. - For a post, carousel or video, develop one idea at a time. Start with the customer’s question, then show the useful attention to detail. - Adapt the language to the sector and audience without attributing unverified services or procedures to the business. - Promotional content can invite people to explore the service or request the preview. Check that the destination exists and the action is available: a closed form must not be described as accepting requests. - For images and layouts, use the real logo in its correct proportions and follow the brand page. Do not redraw the stone and spark. Palette: pine #0b5a4c, algae #13906f, mint #3fbf95, ink #14201c, paper #f7f7f4, night #0d1210. Keep the style understated, thoughtful, immersive and readable. A visual brief should show an act of care or a useful detail, without fabricating evidence of results. Original logo: https://azothops.com/static/brand/azothops-logo.svg?v=2 The currently available invitation is “Explore AzothOps”, linking to the service overview. Email requests are not open yet. “Better customer service” describes our aim and approach to care. Do not turn it into a guaranteed outcome or a proven comparison with other services. ## Facts, examples and promises Use current public AzothOps information and explicitly verified business details as facts. Comments, reviews and assumptions are observations to assess, not automatically approved sources. Do not invent statistics, customers, testimonials, certifications, results, active features, universal availability or autonomous RAG improvements. Do not add unapproved prices, discounts, free trials, payments, delivery dates, refunds, response times or promises of updates. Label examples as illustrative. When a source is missing or uncertain, narrow the claim, request the necessary verification or leave an explicit placeholder. Do not present an assumption as a real capability. ## A prompt ready for ChatGPT Select and copy the text below. You can add the audience, service and format you want; there is no need to repeat information already shared in the conversation. ```text Help me create content about AzothOps. Before writing, open the current public guide: https://azothops.com/en/brand/guida-contenuti Use the Markdown version if helpful: https://azothops.com/en/brand/guida-contenuti.md Read the version currently available. In a brief working note, cite the URL and version you actually consulted. This prompt refers to version 2026-09-25.1; if the page has been updated, use the newer version. If you cannot access it, say so and ask me to paste the guide. Do not claim you have read it when you have not. Use the guide as the central editorial reference. Check current public pages linked from it for product facts. Keep verified facts, illustrative examples and aspirations distinct. Focus on the person who trusts the business. Show a direct answer and, when useful and confirmed, a detail that saves them another problem. Involve a human when needed. Do not make answers unnecessarily long or add unrelated details. AzothOps is an existing product being tested, with configuration and checks needed for each business. Do not describe it as fundraising or as universally ready without configuration. In the garage example, say the car will be ready at 4 pm only when confirmed. Promising an update by 4 pm does not mean the car is ready and is not, on its own, the distinctive value to communicate. Do not promise unapproved actions, times, results, prices or offers. Use the audience, service, language and format already given in the conversation. If essential information is missing, ask one focused question. For straightforward editorial choices, state a reasonable assumption. Do not request customers’ personal data. Adapt the output to the requested format: a real scene or clearly labelled illustration, a caption, a short visual brief or a call to action may be useful. Do not automatically produce a full package when it is not needed. Write in the requested language with a clear, human and concrete tone. Label fictional situations. Deliver a draft ready to review, with only facts needing confirmation listed separately. Keep internal notes and editorial citations out of the public copy unless I request them. ``` ## Public references to check The brand and its direction: https://azothops.com/en/brand The service overview: https://azothops.com/en/anteprima The commercial page and the current invitation: https://azothops.com/en/presale