Change welcome message on MS Teams Now Virtual Agent bot

ayman_h
Kilo Sage

Hi,

We have successfully integrated the Now Virtual Agent MS Teams bot. When a user installs the bot, they get a welcome message on their MS Teams instance saying 'Welcome to Now Virtual Agent....' including the Help commands.

Any idea how we can update this welcome message? I have looked into Message content and sys_notification tables but wasn't be able to find anything related to these message

Regards,

Ayman

1 ACCEPTED SOLUTION

Joel Dias
Kilo Sage

Hello,

The settings are in the sys_cs_provider_application table for your integration.
You need to open the correct channel identity. The messages used are "msteams_welcome_part1_msg" and "msteams_welcome_part1_msg".

For the commands displayed in the help, you can exclude the channel for each command in the integration configuration (Messaging Apps Integation module).

View solution in original post

38 REPLIES 38

Smith Johnson
Kilo Sage

Hello,

we have a similar requirement to change the following greeting message on MS Teams.

SmithJohnson_0-1691661980539.png
Based on what it is mentioned in this thread, we need to go to channel provider.
However, I dont see any bot message.

SmithJohnson_1-1691662128501.png


Does this mean that we need to create one?
And if so, what the name should be? Something like "msteams_welcome_part1_msg" as mentioned before?

Your help would be priceless.

 

Hi Smith,

 

I believe these records were auto created in our case. Also do you get this greeting message everytime you start conversation with VA. If yes, then you should customize the greeting topic setup in your chat experience.

 

Thanks,

Rishi.

Rahul Kumar18
Tera Contributor

What value does this variable contain "$teamsDocUrl"? It is present in msteams_welcome_part2_msg. Where are these variables stored?

rcanvel
Tera Contributor

Hi! In case some of you are still wanting an answer to this. You can find the answer here - Re: Microsoft Teams app disable Virtual Agent Aspe... - ServiceNow Community

I confirmed it works in our SN instance.