Free Salesforce Rev-Con-201 Actual Exam Questions - Question 11 Discussion
ensure successful adoption and maintenance.
Which steps should the consultant take with the customer after go-live?
A/B? Formal knowledge transfer (A) sets a strong foundation, but staying accessible through Slack (B) adds real-time support. Combining both might be the best way to ensure smooth post-go-live handling.
A imo, formal knowledge transfer is crucial because it equips the customer's team with the right info to handle day-to-day issues without always needing consultant help. B’s Slack communication is useful but feels more informal and less structured for long-term adoption. C seems unrealistic since customers may not have time or resources to get certified right after go-live or create detailed docs themselves. So having clear sessions plus documentation (A) covers both immediate and future needs better, making it the most balanced approach for successful adoption and maintenance.
B tbh, keeping in touch via Slack is a good way to stay connected and address any quick issues or questions that pop up after go-live. It helps maintain a direct line for support without waiting for formal meetings. That ongoing communication can catch small problems early before they become bigger.
Also, A is good for initial setup, but real-time interaction through something like Slack ensures the customer feels supported continuously, which is key for adoption and smooth maintenance over time.
A imo, formal training and docs are way more reliable than casual Slack chats.
Makes sense to focus on A here, but I think B can be ruled out because just chatting on Slack isn’t really a formal support plan—it’s too informal for ongoing maintenance. C sounds off since expecting the customer to get certified and write docs is a big ask, especially right after go-live. So, A feels like the most practical step to ensure they’re set up for success without relying on constant consultant involvement.
A imo. Knowledge transfer sessions plus documentation make sure the customer isn’t stuck later on, especially if the consultant isn’t always around. B sounds helpful but feels less structured and might get messy without formal docs or training. C seems a bit much—getting certified might not be realistic for the customer team and doesn’t guarantee they’ll handle maintenance well. Solid training and clear docs usually cover what’s needed after go-live.
Maybe A works better because solid documentation and training help customers become self-sufficient, reducing dependency on the consultant. Slack chats (B) are good but less reliable for structured learning.
Maybe B, since staying connected helps catch issues early and shows ongoing support.
B. Keeping in touch through Slack or another quick communication channel can help catch issues early and show the customer you’re still engaged. This informal ongoing support can complement formal training and docs, making sure problems don’t get ignored after go-live. While A is important, just handing over docs without some personal follow-up might not be enough to ensure smooth adoption. C seems like too much to expect from customers, especially right after implementation.
Makes sense to provide solid knowledge transfer with docs (A) for long-term success.
A/B? A covers formal knowledge transfer, but staying connected via Slack (B) helps catch real-time issues and build rapport, which is important for smooth adoption. C feels a bit much for most customers.
It’s A, plus B seems informal and less structured for ongoing support.
Sounds like it's about ongoing support. A seems the most practical with knowledge sessions and docs after go-live.