Telephones...

For me, I find that the way telephones are managed currently doesn’t work at all. In part it has to do with bad practices in our previous database that translated into bad data in Tessitura, then of course there’s just the fact that every department seems to have different standards. So a lot of this is user error that will need to be corrected.

The number one thing that does not work for us is phones tied to addresses. Most people have cell phones, and list cell phones as their primary number. When someone inactivates an address they might accidently inactivate the phone number unknowingly which leads to a lot of user error. Plus, there’s also the problem that you never quite know who you’re calling.

We’ve tried to remedy some of this by using phones “below the line”, but even there its often confusing. And often we simply don’t know what kind of phone number it is (though there’s not much Tessitura can do about that!)

Here are the different types of phone numbers we need to track:

N1 Cell

N2 Cell

N1 & N2 Home

N1 Business

N2 Business

N1 Assistant

N2 Assistant

N1 & N2 Seasonal Home

Those are just the ones that come to the top of my head. I completely second previous responses about how it’d be great to have phone purposes so you know which one is okay for telemarketing, or texting. It would also be great to use these to track night, daytime, or weekend numbers so you know based on the day and time which is the best number to reach them. Especially since we do all of our calling during business hours, but our telemarketing firm calls at night and on Saturday’s.

I feel like phones should be managed like addresses in their own separate tab with the ability to show purposes, perhaps even months in the case of seasonal phones, and notes. Like for example if I was tracking an Assistant phone I would love to have a space that lets me know Mr. Rich’s assistant name is Tracey because who wants to be referred to as Mr. Rich’s assistant?

-Marta

For me, I find that the way telephones are managed currently doesn’t work at all. In part it has to do with bad practices in our previous database that translated into bad data in Tessitura, then of course there’s just the fact that every department seems to have different standards. So a lot of this is user error that will need to be corrected.

The number one thing that does not work for us is phones tied to addresses. Most people have cell phones, and list cell phones as their primary number. When someone inactivates an address they might accidently inactivate the phone number unknowingly which leads to a lot of user error. Plus, there’s also the problem that you never quite know who you’re calling.

We’ve tried to remedy some of this by using phones “below the line”, but even there its often confusing. And often we simply don’t know what kind of phone number it is (though there’s not much Tessitura can do about that!)

Here are the different types of phone numbers we need to track:

N1 Cell

N2 Cell

N1 & N2 Home

N1 Business

N2 Business

N1 Assistant

N2 Assistant

N1 & N2 Seasonal Home

Those are just the ones that come to the top of my head. I completely second previous responses about how it’d be great to have phone purposes so you know which one is okay for telemarketing, or texting. It would also be great to use these to track night, daytime, or weekend numbers so you know based on the day and time which is the best number to reach them. Especially since we do all of our calling during business hours, but our telemarketing firm calls at night and on Saturday’s.

I feel like phones should be managed like addresses in their own separate tab with the ability to show purposes, perhaps even months in the case of seasonal phones, and notes. Like for example if I was tracking an Assistant phone I would love to have a space that lets me know Mr. Rich’s assistant name is Tracey because who wants to be referred to as Mr. Rich’s assistant?

-Marta