Shouldn't a change in an account's office phone cascade to the related contacts?

[amsugar]

Hi! Thank you for reading.

I was expecting that changes to an account's information would affect its contacts.

So,
(1) I created an account A1,
(2) I created a contact C1 whose account is A1,
(3) I changed A1's office phone,
expecting this change to also change C1's office phone.

But it did NOT.

I ask: shouldn't a change in an account's office phone cascade to the related contacts?

If not, I think this is a problem.
If yes, can you please tell what might be wrong in my procedure?

Thank you.

[malcolmh]

Hi,

Usually Contacts have different tel. no's than the Account, each contact will have their own extension no. If you create a Contact from an Account, you get the Account no. shown as a default value

[amsugar]

Thank you for replying!

Indeed, I notice that when I create contacts from an account, some of the account's contact information is copyed, as I expected.

Unfortunately, further changes, after the creation, have no "down" consequences. I find this wrong. After all, a common distinction between CRM systems and plain contact managers is the cascading of such higher level changes.

I hope that this is acknowledged as a current limitation and that, in the near future, an alternative behavior is made possible.

[BrianSteffens]

I don't consider this a limitation or a problem in any way.

- User creates account with company's address and main phone number
- User creates contact, inherits account information by default
- User finds out contact is actually stationed at another office and has an extension, updates contact record
- Account's address and phone number are now individual contact's specific information?

I don't see how this kind of behavior would be useful at all outside of a specific niche situation.