[IMP] whatsapp: clarify "to" field for test message recipients, remove future tense

[huisit]

documentation task card: https://www.odoo.com/odoo/action-4043/5257364

key changes @ line 181 / 192:

• clarified restrictions on test phone number provided during whatsapp config (max. 5 recipients, unlimited messages)
• added instructions for adding message recipients, link to meta documentation
  • see section header in 17.0 prod

other:

• removed callout and appended first sentence to preceding paragraph
• also removed instances of future tense ("will") to match current style; created follow-up task for full article refresh (https://www.odoo.com/odoo/action-4043/5356551)

This 17.0 PR can be FWP up to master. In the event of a merge conflict, tense changes can be left out for future work.

[robodoo]

[huisit]

Hi @larm-odoo! This PR is ready for review

[larm-odoo]

WOW - what a BEAST of a doc!!!

First, remember to upate the format of the title for this PR. This is not an ADD as it is an improvement We have a format for the titles, so this should be:

[IMP] WhatsApp: Add "to" field and remove future tense

There's a lot of suggestions I made. Some are just stylistic preferences of mine, some are doc standards. Take what you like from the optional suggestions, and make sure the universal updates are done (bold app names, remove center form images, etc).

This is a LOT of info, and I did not create the Meta acocunt to check, so take my suggestions with a grain of salt, since I am not following along on the facebook side =). Please let me know ifyou have any quesitons, and tag me again for another review when done. Thanks!!

[huisit]

@larm-odoo i've implemented your feedback! can you re-review please?

[larm-odoo]

Great updates! I did see a few things that I recommend you double-check. First are the external links. I noticed some appear with the "http:://...." and some are just text, like "Meta developer console". I honestly think the second is better - just seeing the text, and not the URL itself. This can be done by rephrasing anyplace that just shows the URL. So instead of saying "Navitage to the Facebook Meta blah blah blah by going ot (web address). Instead, you can say " "Navitae to the "Facebook Meta blah blah blah" then... and have the part in quotes be the link. I think it's a cleaner way of viewing the information. This woudl require rewriting a lot of the links so it makes sense that the words are the link. Make sense?

Also, lots of th eimages have notations, which we no longer use. If you can retake the images and not add the red call-outs, that would be ideal. Some images I feel are not needed- example. the error images, the text int he error is in the written aprt, so they are redundant (except the first one, I woudl add the missing warning tet to the actual document so you can remove the image). Also, the 'add users to a chat' part - I feel that image is not needed- especialy when you remove the red markups, it'll seem confusing. I think you can eliminate the image and just include 'in the upper-right corner' to navigate them to where the button/icon is.

The image for the template placeholder example - I think that image can be removed, and you can add more text to the example. You cna include the palceholder text (what the user sees) then have the text appear as the receiver would. Make sense? This woudl allow for the elimination of the image.

Basically, if they are very big and uncrooppoed, and ponting out osmethig fairly obvious that you cna describe, I'd remove it. TImages hsoudl help clarify when necessary, but we don't need everything added as a visua;l.

We are almost there! Looking VERY good - and I know configuration instructions outside of Odoo is a pain, I've done it as well, so I appreciate all the work for this!

[larm-odoo]

One more note - this PR title should change to a [IMP] not [ADD] because Add is only used when we are adding a doc that did not exist before, anything we improve or change for existing docs is an [IMP], regardless of how little or how much we change. Unless it's a tiny fix, like ONE typo- that would be a [FIX] PR.

[huisit]

@Felicious

[huisit]

@Felicious this is ready for review, PR and commit have been updated from ADD -> IMP

[Felicious]

What an outstanding first PR, @huisit !

This was a highly technical and challenging piece of content, and the scope alone made it non-trivial. The improvements you’ve made to language, clarity, and structure are substantial. The document is now easy to navigate, easy to search, and straightforward to follow 😄 Seeing the end result, it’s clear why this took time to get right -- the outcome justifies the effort. This is strong work!!

I really liked how you grouped the Quickstart section in particular. It's a term that a lot of companies in our industry uses, so it's easy to focus on the steps and allow users to orient themselves quickly. It's a prime example of how important naming and titling is in your craft of writing!

More broadly, you did a good job filling in missing context and reshaping content that was previously written primarily for highly technical readers. The document now works for less technical users without oversimplifying the material. Even where the overall structure remained similar, the document reads very differently due to clearer language, better prioritization, and thoughtful use of admonition blocks to abstract detail where appropriate. Moving away from raw link displays and consistently using descriptive link text also makes the document feel much cleaner and more intentional.

Overall, this document aligns extremely well with our style guidelines. It’s rare to see a first major doc come in this polished and this well-aligned. The amount of care and iteration you put into this shows 😊 And I barely had to do anything for my review!

After you look over some really minor changes I pointed out, this is ready for merge!

@robodoo delegate+

[Felicious]

Are we italicizing or bolding the step names on the whatsapp side? You can make the call, but i just want us to be consistent, as it was bolded back on line 301

Here on line 363

[Felicious]

@robodoo fw=no

[robodoo]

Disabled forward-porting.

[huisit]

@robodoo r+